Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-12084 is a critical-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Samba Rsync. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked in the top 0.6% 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 SI-10 (Information Input Validation) — 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 heap-based buffer overflow vulnerability, tracked as CVE-2024-12084, affects the rsync daemon. The flaw stems from improper handling of attacker-controlled checksum lengths (s2length) in the code, which allows an out-of-bounds write to the sum2 buffer when MAX_DIGEST_LEN exceeds the fixed SUM_LENGTH of 16 bytes. It is assigned CWE-122 and CWE-787 and carries a CVSS 3.1 score of 9.8.
An unauthenticated remote attacker can exploit the issue over the network by sending a crafted checksum length value to a vulnerable rsync daemon. Successful exploitation can result in arbitrary code execution, data corruption, or a crash, granting the attacker full confidentiality, integrity, and availability impact on the affected system.
Red Hat has published advisory RHBA-2025:6470 and a corresponding CVE entry that direct users to apply the available errata packages. Additional details appear in the Red Hat Bugzilla entry, CERT VU#952657, and the oss-security mailing list posting from January 2025.
The associated EPSS score remains low, with a current value of 0.0488 and a peak of 0.0507.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-50580
Vulnerability Data
A heap-based buffer overflow flaw was found in the rsync daemon. This issue is due to improper handling of attacker-controlled checksum lengths (s2length) in the code. When MAX_DIGEST_LEN exceeds the fixed SUM_LENGTH (16 bytes), an attacker can write out of…
more
bounds in the sum2 buffer.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.4.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including fuzzing and memory-error detectors) can discover heap overflows after they have been coded.
Input validation enforces bounds checking on data written to heap buffers, directly stopping the overflow condition from being introduced.
Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.
Security engineering principles require use of memory-safe constructs and bounds-checked allocation routines that avoid introducing heap overflows.
Memory-protection mechanisms limit the ability of a heap overflow to execute attacker-controlled code or corrupt adjacent structures.
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.
Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.
Timely patching removes known heap-overflow instances after they exist.
Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.
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.