CVE-2024-12747: Rsync: race condition in rsync handling symbolic links
A flaw was found in rsync. This vulnerability arises from a race condition during rsync's handling of symbolic links. Rsync's default behavior when encountering symbolic links is to skip them. If an attacker replaced a regular file with a symbolic link at the right time, it was possible to bypass the default behavior and traverse symbolic links. Depending on the privileges of the rsync process, an attacker could leak sensitive information, potentially leading to privilege escalation.
Security readout for executives and security teams
Plain-English summary
CVE-2024-12747 is a race condition in rsync’s handling of symbolic links. A local, low-privileged attacker could potentially cause rsync to follow a symlink it would normally skip, exposing sensitive files if rsync runs with higher privileges. The issue is rated medium, but impact depends heavily on how rsync is used.
Executive priority
Treat as a targeted hardening and patch-management item, not an internet-wide emergency. Prioritize servers where rsync runs as root or another privileged account and processes files writable by less-trusted users. Confidentiality exposure is the main business concern.
Technical view
The flaw is CWE-362: a race condition during rsync symlink handling. By changing a regular file to a symlink at a narrow timing window, an authenticated local attacker could bypass rsync’s default symlink-skipping behavior. CVSS is 5.6: local access, high attack complexity, low privileges required, no user interaction, high confidentiality impact.
Likely exposure
Exposure is most relevant on systems running rsync where untrusted local users can modify files processed by privileged rsync jobs. The bundle lists affected Red Hat Enterprise Linux 8, 9, 10, Red Hat Discovery 1.14, and Red Hat OpenShift Container Platform 4 rhcos. RHEL 6 and 7 status is listed as unknown.
Exploitation context
No active exploitation is stated in the provided sources, and the CVE is not marked as KEV. Exploitation requires local access, low privileges, and successful timing of a race condition. The main risk is sensitive information disclosure, with possible privilege escalation depending on rsync process privileges and file access scope.
Researcher notes
The provided data supports a local, high-complexity symlink race with high confidentiality impact. Affected product detail is strongest for Red Hat entries in the bundle. External references include CERT/CC, Debian LTS, and NetApp advisories, but the bundle does not provide their specific affected-version details.
Mitigation direction
Apply applicable vendor updates from Red Hat errata for affected products.
Check Debian, NetApp, and other vendor advisories if those platforms use rsync.
Prioritize privileged rsync jobs processing user-writable or shared directories.
Run rsync with the least privileges practical for the business workflow.
Restrict local write access to directories consumed by privileged rsync jobs.
If no update is available, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory systems and containers with rsync installed.
Compare installed rsync packages against vendor advisory affected and fixed versions.
Identify scheduled or service-run rsync jobs with elevated privileges.
Review whether rsync input paths are writable by untrusted local users.
Confirm OpenShift rhcos and Discovery deployments against Red Hat advisory applicability.
Document exceptions where vendor status is unknown, especially RHEL 6 and 7.
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 · low confidence lookup
CWE-362: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 privilege impact, so privilege escalation and authorization behavior 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-362 · source CWE mapping
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.