CVE-2024-12085
Redhat Enterprise Linux Server For Power Little Endian Update Services For Sap Solutions 8.4_ppc64le … 9.6_ppc64le
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2024-12085 is a high-severity Use of Uninitialized Resource (CWE-908) vulnerability in Redhat Enterprise Linux Server For Power Little Endian Update Services For Sap Solutions. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked in the top 5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
A flaw in rsync allows an attacker to manipulate the checksum length value (s2length) during file checksum comparisons. This triggers a comparison against uninitialized memory and leaks one byte of stack data at a time. The issue is tracked as CVE-2024-12085, carries a CVSS score of 7.5, and is classified under CWE-908 (Use of Uninitialized Resource). It affects the rsync utility when processing remote or untrusted file transfers that involve checksum verification.
An unauthenticated network attacker can exploit the vulnerability by sending crafted checksum data, achieving incremental disclosure of uninitialized stack contents without requiring user interaction or elevated privileges. The impact is limited to confidentiality, but repeated requests can accumulate sensitive memory fragments over time.
Red Hat has published multiple errata (RHSA-2025:0324, RHSA-2025:0325, RHSA-2025:0637, RHSA-2025:0688, and RHBA-2025:6470) that deliver patched rsync packages; administrators should apply the updates through standard update channels to eliminate the flaw.
The associated EPSS score currently stands at 0.1902 with a recorded peak of 0.2148, indicating moderate and relatively stable exploitation interest since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-50581
Vulnerability Data
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…
more
of uninitialized stack data at a time.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including static analysis) can find uses of uninitialized resources after they are coded.
Requiring documented development standards and tools can mandate initialization checks and safe patterns that stop the weakness from being introduced.
Engineering principles can require explicit resource initialization before use, structurally avoiding uninitialized access.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC activities such as static analysis and code review directly prevent use of uninitialized resources while also addressing many other weaknesses.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect uninitialized resource usage through dynamic analysis and fuzzing.
Secure development life cycle mandates initialization checks and static analysis that can catch uninitialized resource use.
Application security requirements can specify mandatory initialization of variables and resources before use.
Secure system architecture and engineering principles include defensive coding practices that prevent use of uninitialized memory or objects.
Secure coding standards directly require explicit initialization of all variables and resources, substantially mitigating CWE-908.