Path Traversal in langchain (CVE-2024-7774)
Summary
Path traversal in langchain (CVE-2024-7774). Risk of unauthorized operations or information disclosure. Exploitable via getFullPath. Mitigation: upgrade to 0.2.19 or later.
Original description
The description as published by the source.
A path traversal vulnerability exists in the getFullPath method of langchain-ai/langchainjs version 0.2.5. This vulnerability allows attackers to save files anywhere in the filesystem, overwrite existing text files, read .txt files, and delete files. The vulnerability is exploited through the setFileContent, getParsedFile, and mdelete methods, which do not properly sanitize user input.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-7774 has been found in langchain.
Attackers can target a specific entry point like getFullPath over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade langchain to 0.2.19 or later.
If unsure, ask your IT team or search "langchain CVE-2024-7774" on the vendor's site.
CVE-2024-7774 (langchain) — CWE-22
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: getFullPath / setFileContent / getParsedFile / mdelete
Patched: 0.2.19 — apply immediately
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.
Path traversal (CWE-22) exists in langchain. Attackers reach the vulnerable code path via getFullPath without authentication.
Check the vendor advisory for the affected versions of langchain. Attack surface: getFullPath / setFileContent / getParsedFile / mdelete.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.2.19.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'langchain' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'langchain' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
langchainを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade langchain to 0.2.19ステージング環境で 0.2.19 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web huntr.com