Path Traversal in Plandex 2.2.1 Allows Arbitrary File Write

Executive Summary

Plandex 2.2.1 has a path traversal flaw in the ApplyFiles function. It allows attackers to write files outside the project directory by manipulating model output or repository files. Paths like ../../../etc/cron.d/x can escape the project root, enabling writes to sensitive locations such as shell startup files or cron jobs, which could lead to code execution.

Useful 0 Not Useful 0

Detection Guidance

Check Plandex version with `plandex --version` or inspect logs for suspicious file writes outside project directories. Monitor for unexpected changes in system files like ~/.bashrc, /etc/cron.d/, or other sensitive locations. Review apply operations for paths containing parent directory segments (e.g., ../../../).

Useful 0 Not Useful 0

Impact Analysis

An attacker could write malicious files to critical system locations like ~/.bashrc or /etc/cron.d/x. This could allow arbitrary code execution, enabling the attacker to gain control over the system where Plandex runs. The risk is higher with auto-apply modes that bypass user confirmation.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability could violate compliance with GDPR and HIPAA by enabling unauthorized file writes to sensitive locations. Attackers could write to shell rc files or cron jobs, potentially executing malicious code with user privileges. This may lead to unauthorized data access, modification, or exfiltration, violating data protection requirements under GDPR (e.g., integrity and confidentiality principles) and HIPAA (e.g., safeguards for protected health information).

Useful 0 Not Useful 0

Mitigation Strategies

Upgrade Plandex to a patched version beyond 2.2.1. Disable auto-apply mode to require manual confirmation for file writes. Implement path containment checks in the ApplyFiles function to reject absolute paths and parent directory segments. Display resolved destination paths in apply prompts for transparency.

Useful 0 Not Useful 0