← back
CVE-2024-12084criticalCWE-122

Rsync: heap buffer overflow in rsync due to improper checksum length handling

70Vexday Risk Score

Keep watching. It has a public proof of concept.

ssvc Attendcvss 9.8epss 72%
from disclosure to weapon6 days
Published on NVDJan 15
1st PoC+6d
exploitation probability
72%top 1% of all CVEs
observed exploitation
nono source reports it
4 public exploit(s)
In short

Rsync has a critical flaw where an attacker can crash the service or potentially run malicious code by sending specially crafted data that overflows a buffer used for checksums. This happens because the program doesn't properly limit how much data it writes to memory.

Technical detail

A heap buffer overflow in rsync's checksum handling allows an attacker to write beyond the bounds of the sum2 buffer when MAX_DIGEST_LEN exceeds SUM_LENGTH (16 bytes). The vulnerability stems from improper validation of attacker-controlled s2length parameters, enabling remote code execution or denial of service against rsync daemon instances.

Summary generated and translated by AI from the official description.
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.