CVE-2024-12085: Rsync: info leak via uninitialized stack contents
A flaw was found in rsync which could be triggered when rsync compares file checksums. This flaw allows an attacker to manipulate the checksum length (s2length) to cause a comparison between a checksum and uninitialized memory and leak one byte of uninitialized stack data at a time.
Security readout for executives and security teams
Plain-English summary
CVE-2024-12085 is an rsync information leak. A remote attacker may cause rsync to compare checksums against uninitialized stack memory, leaking small pieces of memory one byte at a time. The main business concern is confidentiality exposure on systems using affected rsync packages, especially where rsync is reachable over a network.
Executive priority
Patch in the normal high-severity security window, faster for exposed rsync services or sensitive environments. This is primarily a data confidentiality risk, not a ransomware-style availability issue. Lack of KEV evidence lowers emergency urgency, but network reachability and no-auth CVSS characteristics justify prompt remediation.
Technical view
The flaw is CWE-908 in rsync checksum comparison handling. Manipulating checksum length, identified as s2length, can trigger comparison with uninitialized stack contents and disclose one byte per interaction. CVSS 3.1 is 7.5: network reachable, low complexity, no privileges, no user interaction, high confidentiality impact, no integrity or availability impact.
Likely exposure
Exposure is most relevant to Red Hat Enterprise Linux 6 ELS, 7 ELS, 8, 9, 10, and listed OpenShift/RHCOS releases carrying affected rsync packages. Internet- or partner-facing rsync services deserve priority review. Non-Red Hat exposure is not established by the provided sources.
Exploitation context
The CVE record describes remote, unauthenticated exploitation characteristics by CVSS. The provided bundle does not show CISA KEV listing or cited evidence of active exploitation. Treat this as a serious confidentiality issue, but do not assume confirmed in-the-wild exploitation from these sources alone.
Researcher notes
The provided detail is enough to classify the bug as an uninitialized stack disclosure during checksum comparison. Sources do not provide safe reproducer details, fixed upstream version boundaries, or evidence of exploitation. Validate exposure through package provenance and vendor errata rather than assuming all rsync deployments are affected.
Mitigation direction
Apply the relevant Red Hat security or bug-fix errata for affected RHEL and OpenShift assets.
Prioritize externally reachable rsync services and systems handling sensitive data.
If no listed erratum applies, check the operating system or appliance vendor guidance.
Restrict rsync network exposure where business operations allow.
Review authentication and access controls around rsync services.
Validation and detection
Inventory systems with rsync installed, including RHEL, RHCOS, and OpenShift nodes.
Map package versions to the affected Red Hat product list and errata.
Confirm applicable vendor errata have been installed successfully.
Identify rsync services reachable from untrusted networks.
Monitor vendor advisories for updated affected-version and fix information.
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-908: 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 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-908 · source CWE mapping
Use of Uninitialized Resource
Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.