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 bounds in the sum2 buffer.
Workaround:
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
The product writes data past the end, or before the beginning, of the intended buffer.
Link | Tags |
---|---|
https://access.redhat.com/errata/RHBA-2025:6470 | vendor advisory |
https://access.redhat.com/security/cve/CVE-2024-12084 | third party advisory vdb entry |
https://bugzilla.redhat.com/show_bug.cgi?id=2330527 | third party advisory issue tracking |
https://kb.cert.org/vuls/id/952657 | third party advisory |
http://www.openwall.com/lists/oss-security/2025/01/14/6 | mailing list third party advisory |
https://github.com/google/security-research/security/advisories/GHSA-p5pg-x43v-mvqj | exploit vendor advisory |