Loading vulnerability…
CVE-2024-12084 is a critical heap-based buffer overflow in the rsync daemon affecting rsync versions prior to 3.4.0, with some reporting narrowing the affected range to versions 3.2.7 through 3.3.0. The flaw is caused by improper handling and validation of an attacker-controlled checksum length value, s2length. When the configured or compiled maximum digest length exceeds the fixed SUM_LENGTH of 16 bytes, the daemon can perform an out-of-bounds write into the sum2 heap buffer. Because the vulnerable code processes attacker-influenced checksum metadata during rsync daemon operations, a remote attacker can corrupt heap memory. The issue affects the server-side daemon implementation and does not affect the rsync client application.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository contains a single Python exploit script (CVE-2024-12084.py) and a brief README. The script is a proof-of-concept exploit for CVE-2024-12084, targeting the rsync file synchronization daemon (likely version 31.0 and possibly others). The exploit automates the rsync protocol handshake, module negotiation, and file transfer process, aiming to retrieve files from the server, such as a 'flag' file, by exploiting a vulnerability in the rsync daemon. The script can operate in both local and remote modes, connecting to a specified IP and port or launching a local rsync process for testing. It interacts directly with the rsync protocol, handling handshake, argument negotiation, and file data reception, and is designed for use by security researchers to demonstrate the vulnerability. The only network endpoint hardcoded is 127.0.0.1:8730 for local testing, but the script can be adapted to target remote servers. No detection or fake exploit code is present; this is a functional proof-of-concept exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
One of a set of Rsync daemon vulnerabilities (Rsync <= 3.3.0) that can contribute to remote code execution, directory traversal, and/or sensitive information disclosure.
A vulnerability in rsync addressed by updating to version 3.4.1.
A heap overflow vulnerability in rsync (versions >= 3.2.7 and < 3.4.0) that could allow remote code execution if exploited. This is the most severe of the six vulnerabilities announced for rsync in January 2025.
An rsync server vulnerability that can lead to remote code execution.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.