CVE-2024-7774

What it actually does

Path traversal in getFullPath allows unsanitized user input to reach setFileContent, getParsedFile, and mdelete, enabling arbitrary file read, write, overwrite, and deletion anywhere on the filesystem.

Why it matters to the business

Attackers can exfiltrate sensitive data, tamper with configuration or application files, and delete critical assets, resulting in service disruption, compliance violations, and potential full system compromise.

How an attack unfolds

An attacker supplies crafted relative or absolute paths containing traversal sequences to the affected methods; the library fails to canonicalize or restrict the resulting paths, allowing direct filesystem operations outside intended directories.

How to fix it

Upgrade langchain-ai/langchainjs to commit a0fad77d6b569e5872bd4a9d33be0c0785e538a9 or later; validate that all file-path inputs are normalized and confined to allowed directories before calling the affected methods.

How to confirm the fix worked

Confirm the library version is at or above the fixed commit; test that traversal sequences in inputs are rejected or normalized to safe paths; review application logs for any prior use of the vulnerable methods with suspicious path arguments.

Typical attack path

1. Identify an application or integration using vulnerable langchainjs file-handling methods
2. Craft input containing path traversal sequences targeting sensitive files
3. Invoke setFileContent to write or overwrite arbitrary files
4. Use getParsedFile to read .txt contents
5. Call mdelete to remove chosen files

How to detect it

Review application and web-server logs for unusual file paths containing .. or absolute paths passed to langchainjs file methods; inspect file-system timestamps and ownership changes on sensitive files; search process execution logs for node processes performing unexpected read/write/delete operations on non-application directories.

What your security team should do

• Immediately upgrade langchainjs to the fixed commit in all environments
• Audit code for direct or indirect calls to setFileContent, getParsedFile, and mdelete
• Implement input sanitization and path allow-listing as defense-in-depth
• Monitor dependency updates and scan for other path-handling libraries with similar patterns