Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalPublic exploit

Heap-based Buffer Overflow in rsync daemon

IdentifiersCVE-2024-12084CWE-122· Heap-based Buffer Overflow

CVE-2024-12084 is a heap-based buffer overflow in the rsync daemon (rsyncd). The flaw is caused by improper handling of attacker-controlled checksum length values (s2length). According to the provided content, when MAX_DIGEST_LEN exceeds the fixed SUM_LENGTH of 16 bytes, the daemon can perform an out-of-bounds write into the sum2 buffer. The issue affects the server-side rsync daemon implementation and not the rsync client application. Multiple sources in the provided content describe this as the most critical of the disclosed rsync flaws and state that it can lead to remote code execution on the target server.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can corrupt heap memory in the rsync daemon process and may lead to remote code execution on the vulnerable target server. The provided content consistently characterizes this issue as critical and notes that the server-side vulnerabilities CVE-2024-12084 and CVE-2024-12085 can result in RCE. Because the flaw is in the daemon, impact is on systems exposing rsyncd rather than client-only deployments.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure of the rsync daemon by disabling rsyncd where not required, blocking or tightly restricting access to TCP port 873, and limiting access to trusted hosts or management networks only. The content also recommends restricting network exposure and monitoring rsync processes for unusual command execution as a detection measure. These steps are mitigations only and do not remove the underlying memory corruption flaw.

Remediation

Patch, then assume compromise.

Upgrade rsync to a fixed release. The provided content states that rsync security updates in version 3.4.1 address CVE-2024-12084, and other content recommends upgrading to a patched upstream release in the 3.4.x line. Linux distribution users should install vendor-supplied patched packages rather than relying solely on upstream source guidance. Where applicable, apply product-specific updates that bundle fixed rsync components.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).

VALID 1 / 3 TOTALView more in app
CVE-2024-12084MaturityPoCVerified exploit

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.

InkeyPDisclosed Nov 24, 2025pythonnetwork
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AlmalinuxAlmalinuxoperating_system
ArchlinuxArch Linuxoperating_system
GentooLinuxoperating_system
HPE Aruba NetworkingManagement Software (Airwave)application
NixosNixosoperating_system
NovellSuse Linuxoperating_system
Red HatEnterprise Linuxoperating_system
SambaRsyncapplication
TritondatacenterSmartosoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity8

Community discussion across Reddit, Mastodon, and other social sources.