CVE-2024-12087: Rsync: path traversal vulnerability in rsync
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.
Security readout for executives and security teams
Plain-English summary
CVE-2024-12087 lets a malicious rsync server cause a client to write files outside the folder the client intended. This can affect systems that pull backups, mirrors, or software content from rsync servers. The rated severity is medium, but business impact can be significant where rsync runs with broad file permissions.
Executive priority
Prioritize patching where rsync pulls data into sensitive servers, build systems, backup hosts, or privileged automation. Treat internet or third-party rsync sources as higher urgency. Lower priority may be reasonable for systems that do not run rsync clients or only sync from trusted internal servers.
Technical view
This is a CWE-22 path traversal issue in rsync tied to --inc-recursive behavior. Inadequate symlink verification and per-file-list deduplication checks can let a server write files outside the client destination directory. CVSS is 6.5: network reachable, low complexity, no privileges, user interaction required, high integrity impact.
Likely exposure
Exposure is most relevant to clients that connect to untrusted or compromised rsync servers. The bundle lists affected Red Hat Enterprise Linux 6 ELS, 7 ELS, 8, 9, 10, Red Hat Discovery 1.14, and OpenShift Container Platform 4 rhcos packages. Other vendors may be affected; check their advisories.
Exploitation context
The attacker needs the victim to run rsync as a client against a malicious server. The CVE is not listed as KEV in the provided data, so active exploitation is not established here. A Google security advisory is referenced, indicating public technical detail exists.
Researcher notes
Key conditions are client-side rsync operation, --inc-recursive behavior, server-controlled file lists, symlink handling, and destination escape. The provided data does not prove arbitrary code execution or confidentiality impact. Validate product status through vendor advisories because affected packaging differs by distribution and platform.
Mitigation direction
Apply relevant vendor rsync updates, including applicable Red Hat RHSA or RHBA errata.
For non-Red Hat systems, check CERT and vendor advisories for fixed package guidance.
Avoid pulling rsync content from untrusted servers until systems are updated.
Review automated backup, mirror, and deployment jobs that use rsync clients.
Validation and detection
Inventory systems with rsync installed, especially Red Hat and OpenShift environments listed as affected.
Compare installed package versions against the vendor CVE page and errata.
Identify rsync jobs that pull from external, third-party, or less-trusted servers.
Confirm updates were installed through standard package or platform compliance reporting.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.