Sign in Sign up
JA · EN · FR
SecPulse
← Back
GHSA-j4r7-8ph4-43g3

Path Traversal in faf-mcp (GHSA-j4r7-8ph4-43g3)

Summary

path traversal in faf-mcp (GHSA-j4r7-8ph4-43g3). Risk of unauthorized operations or information disclosure. Exploitable via ``path``. Mitigation: upgrade to `2.1.3` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **GHSA-j4r7-8ph4-43g3** has been found in faf-mcp. Attackers can target a specific entry point like ``path`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade faf-mcp to **2.1.3** or later. If unsure, ask your IT team or search "faf-mcp GHSA-j4r7-8ph4-43g3" on the vendor's site.
GHSA-j4r7-8ph4-43g3 (faf-mcp) — CWE-22 / Attack surface: `path` / `faf_read` / `faf_write` / `FAF_ALLOWED_ROOTS` Patched: `2.1.3` — apply immediately Workaround: If you cannot upgrade immediately, run the server only against trusted local projects, and set `FAF_ALLOWED_ROOTS` (patched versions) to a single project directory for a hard directory boundary. Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in faf-mcp. Attackers reach the vulnerable code path via ``path`` without authentication.
📍 Affected scope
faf-mcp — . Attack surface: `path` / `faf_read` / `faf_write` / `FAF_ALLOWED_ROOTS`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.1.3**.
🛡️ Workaround
Workaround: If you cannot upgrade immediately, run the server only against trusted local projects, and set `FAF_ALLOWED_ROOTS` (patched versions) to a single project directory for a hard directory boundary.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'faf-mcp' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'faf-mcp' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `faf-mcp` を grep し、稼働しているサービス・バージョンを把握する。

  2. 5
    Apply temporary workaround mitigate 
    If you cannot upgrade immediately, run the server only against trusted local projects, and set `FAF_ALLOWED_ROOTS` (patched versions) to a single project directory for a hard directory boundary.

    パッチが適用されるまでの応急処置として、If you cannot upgrade immediately, run the server only against trusted local projects, and set `FAF_ALLOWED_ROOTS` (patched versions) to a single project directory for a hard directory boundary. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch 
    Upgrade faf-mcp to 2.1.3

    ステージング環境で 2.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm faf-mcp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.3"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →