CVE-2024-12087: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
A path traversal vulnerability exists in rsync. It stems from behavior enabled by the `--inc-recursive` option, a default-enabled option for many client options and can be enabled by the server even if not explicitly enabled by the client. When using the `--inc-recursive` option, a lack of proper symlink verification coupled with deduplication checks occurring on a per-file-list basis could allow a server to write files outside of the client's intended destination directory. A malicious server could write malicious files to arbitrary locations named after valid directories/paths on the client.
AI Analysis
Technical Summary
CVE-2024-12087 is a path traversal vulnerability discovered in the widely used rsync utility, specifically tied to the behavior of the --inc-recursive option. Rsync is a popular tool for efficient file synchronization and transfer, often used in backup and deployment workflows. The --inc-recursive option, which is enabled by default in many client configurations and can be enforced by the server, is designed to incrementally recurse through directories. However, this option lacks adequate verification of symbolic links and performs deduplication checks on a per-file-list basis rather than globally. This flawed logic allows a malicious rsync server to craft file lists that cause the client to write files outside the intended destination directory by exploiting symlink traversal. Consequently, the server can place or overwrite files arbitrarily on the client system, potentially leading to integrity compromise. The vulnerability does not affect confidentiality or availability directly but poses a significant risk to the integrity of client systems. Exploitation requires the client to initiate a connection and interact with a malicious or compromised rsync server, but no prior authentication or elevated privileges on the client side are necessary. The CVSS 3.1 base score is 6.5, reflecting medium severity with network attack vector, low attack complexity, no privileges required, and user interaction needed. No public exploits have been reported yet, but the vulnerability is published and recognized by security authorities. The lack of patch links suggests that mitigation may currently rely on configuration changes or updates pending from rsync maintainers.
Potential Impact
For European organizations, the impact of CVE-2024-12087 can be significant, especially for those relying on rsync for backup, file synchronization, or deployment tasks across networks. A successful exploitation could allow a malicious or compromised rsync server—potentially an external service provider or a man-in-the-middle attacker—to write or overwrite files outside the intended directories on client machines. This can lead to unauthorized code execution, persistence mechanisms, or tampering with critical configuration files, undermining system integrity. While confidentiality and availability are not directly impacted, the integrity breach can facilitate further attacks or disrupt business operations. Organizations with automated rsync workflows or those using rsync in multi-tenant or cloud environments are particularly at risk. The medium severity score indicates a moderate but actionable threat that should be addressed promptly to prevent potential lateral movement or supply chain compromise within European IT infrastructures.
Mitigation Recommendations
1. Immediately audit all rsync client configurations to identify usage of the --inc-recursive option and assess whether it can be disabled or restricted. 2. Where possible, upgrade rsync to the latest version once patches addressing CVE-2024-12087 are released by maintainers. 3. Restrict rsync client connections to trusted servers only, using network-level controls such as firewall rules, VPNs, or SSH key restrictions to prevent connections to untrusted or unknown servers. 4. Implement file system monitoring on client machines to detect unexpected file writes outside authorized directories, focusing on locations rsync is expected to write to. 5. Use containerization or sandboxing techniques for rsync client operations to limit the impact of potential path traversal exploitation. 6. Educate users and administrators about the risks of connecting to untrusted rsync servers and enforce policies to avoid such connections. 7. Monitor security advisories from rsync maintainers and apply patches promptly once available. 8. Consider alternative secure file synchronization tools if immediate mitigation is not feasible.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Italy, Spain, Poland
CVE-2024-12087: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Description
A path traversal vulnerability exists in rsync. It stems from behavior enabled by the `--inc-recursive` option, a default-enabled option for many client options and can be enabled by the server even if not explicitly enabled by the client. When using the `--inc-recursive` option, a lack of proper symlink verification coupled with deduplication checks occurring on a per-file-list basis could allow a server to write files outside of the client's intended destination directory. A malicious server could write malicious files to arbitrary locations named after valid directories/paths on the client.
AI-Powered Analysis
Technical Analysis
CVE-2024-12087 is a path traversal vulnerability discovered in the widely used rsync utility, specifically tied to the behavior of the --inc-recursive option. Rsync is a popular tool for efficient file synchronization and transfer, often used in backup and deployment workflows. The --inc-recursive option, which is enabled by default in many client configurations and can be enforced by the server, is designed to incrementally recurse through directories. However, this option lacks adequate verification of symbolic links and performs deduplication checks on a per-file-list basis rather than globally. This flawed logic allows a malicious rsync server to craft file lists that cause the client to write files outside the intended destination directory by exploiting symlink traversal. Consequently, the server can place or overwrite files arbitrarily on the client system, potentially leading to integrity compromise. The vulnerability does not affect confidentiality or availability directly but poses a significant risk to the integrity of client systems. Exploitation requires the client to initiate a connection and interact with a malicious or compromised rsync server, but no prior authentication or elevated privileges on the client side are necessary. The CVSS 3.1 base score is 6.5, reflecting medium severity with network attack vector, low attack complexity, no privileges required, and user interaction needed. No public exploits have been reported yet, but the vulnerability is published and recognized by security authorities. The lack of patch links suggests that mitigation may currently rely on configuration changes or updates pending from rsync maintainers.
Potential Impact
For European organizations, the impact of CVE-2024-12087 can be significant, especially for those relying on rsync for backup, file synchronization, or deployment tasks across networks. A successful exploitation could allow a malicious or compromised rsync server—potentially an external service provider or a man-in-the-middle attacker—to write or overwrite files outside the intended directories on client machines. This can lead to unauthorized code execution, persistence mechanisms, or tampering with critical configuration files, undermining system integrity. While confidentiality and availability are not directly impacted, the integrity breach can facilitate further attacks or disrupt business operations. Organizations with automated rsync workflows or those using rsync in multi-tenant or cloud environments are particularly at risk. The medium severity score indicates a moderate but actionable threat that should be addressed promptly to prevent potential lateral movement or supply chain compromise within European IT infrastructures.
Mitigation Recommendations
1. Immediately audit all rsync client configurations to identify usage of the --inc-recursive option and assess whether it can be disabled or restricted. 2. Where possible, upgrade rsync to the latest version once patches addressing CVE-2024-12087 are released by maintainers. 3. Restrict rsync client connections to trusted servers only, using network-level controls such as firewall rules, VPNs, or SSH key restrictions to prevent connections to untrusted or unknown servers. 4. Implement file system monitoring on client machines to detect unexpected file writes outside authorized directories, focusing on locations rsync is expected to write to. 5. Use containerization or sandboxing techniques for rsync client operations to limit the impact of potential path traversal exploitation. 6. Educate users and administrators about the risks of connecting to untrusted rsync servers and enforce policies to avoid such connections. 7. Monitor security advisories from rsync maintainers and apply patches promptly once available. 8. Consider alternative secure file synchronization tools if immediate mitigation is not feasible.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- redhat
- Date Reserved
- 2024-12-03T08:58:04.170Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d9816c4522896dcbd6699
Added to database: 5/21/2025, 9:08:38 AM
Last enriched: 10/12/2025, 3:52:44 AM
Last updated: 10/15/2025, 8:10:22 PM
Views: 20
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-11568: Improper Validation of Specified Quantity in Input in Red Hat Red Hat Enterprise Linux 10
MediumCVE-2025-62375: CWE-295: Improper Certificate Validation in in-toto go-witness
MediumCVE-2025-11832: CWE-770 Allocation of Resources Without Limits or Throttling in Azure Access Technology BLU-IC2
CriticalWireTap and Battering RAM: attacks on TEEs | Kaspersky official blog
MediumCVE-2024-6592: CWE-306 Missing Authentication for Critical Function in WatchGuard Authentication Gateway
CriticalActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.