CVE-2024-12088: Rsync: --safe-links option bypass leads to path traversal
A flaw was found in rsync. When using the `--safe-links` option, the rsync client fails to properly verify if a symbolic link destination sent from the server contains another symbolic link within it. This results in a path traversal vulnerability, which may lead to arbitrary file write outside the desired directory.
Security readout for executives and security teams
Plain-English summary
CVE-2024-12088 is an rsync path traversal flaw affecting clients using the --safe-links option. A malicious or compromised rsync server could cause files to be written outside the intended destination directory. Business urgency is moderate unless your environment pulls data from untrusted or externally controlled rsync servers.
Executive priority
Treat as a targeted integrity risk, not a broad emergency. Prioritize patching and workflow review where rsync pulls data from outside your administrative control, especially backup, deployment, and automation systems. Lower urgency applies to environments that do not use rsync clients with --safe-links or only sync from trusted internal servers.
Technical view
The rsync client does not fully validate symbolic-link destinations when --safe-links is used, specifically when the destination path contains another symlink. This can bypass intended link safety checks and allow arbitrary file write outside the transfer directory. CVSS is 6.5, with network attack vector, low complexity, no privileges, user interaction required, and high integrity impact.
Likely exposure
Exposure is most likely on systems running affected rsync packages that pull from untrusted, semi-trusted, or compromised rsync servers with --safe-links enabled. Red Hat lists affected RHEL 8, 9, 10, OpenShift Container Platform 4 rhcos, and Red Hat Discovery 1.14 components; RHEL 6 and 7 status is unknown in the provided data.
Exploitation context
The attacker needs control of, or influence over, the rsync server content. A client must initiate a transfer using --safe-links. No CISA KEV listing is provided, so active exploitation should not be assumed. A public Google Security Research advisory is referenced, indicating public technical analysis exists.
Researcher notes
This is CWE-22 path traversal through incomplete symlink validation in rsync client behavior. The provided data supports arbitrary file write outside the desired directory, not code execution by itself. Affected-version detail is strongest for Red Hat products; broader upstream and vendor fix details should be confirmed from each advisory.
Mitigation direction
Apply vendor updates from Red Hat, Debian, NetApp, or your platform maintainer where applicable.
Prioritize clients that sync from internet-facing, third-party, or lower-trust rsync servers.
Avoid using --safe-links with untrusted rsync servers until vendor guidance is applied.
Review rsync automation for destination paths that contain or depend on symlinks.
If no update is available, follow vendor-specific hardening or workaround guidance.
Validation and detection
Inventory rsync versions and packages across Linux servers, appliances, containers, and base images.
Search scripts, cron jobs, CI jobs, and backup workflows for --safe-links usage.
Identify rsync clients pulling from external or administratively separate servers.
Confirm applicable vendor advisories are installed or documented as not applicable.
Check Red Hat package status for listed affected RHEL, OpenShift, and Discovery components.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.