Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2024-12084: Rsync: heap buffer overflow in rsync due to improper checksum length handling

CriticalCVSS 9.8 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: This week (action score 61/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 72.5% (FIRST EPSS); higher than 99.4% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: azl3 rsync 3.2.7-1 on Azure Linux 3.0 3.4.1-1; azl3 rsync 3.4.1-1 on Azure Linux 3.0 3.4.1-1; cbl2 rsync 3.2.5-1 on CBL Mariner 2.0 3.4.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Don’t wait for the next maintenance window. Upgrade to azl3 rsync 3.2.7-1 on Azure Linux 3.0 3.4.1-1; azl3 rsync 3.4.1-1 on Azure Linux 3.0 3.4.1-1; cbl2 rsync 3.2.5-1 on CBL Mariner 2.0 3.4.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jan 15, 2025
Updated
Nov 4, 2026
EPSS
72.5% · 99th percentile

Report tools

JSON

Action score

61

This week

Don’t wait for the next maintenance window.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
22 / 30 · 72.5%

CISA SSVC decision

Exploitation
proof of concept
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · redhat
9.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-12084

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for samba records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
sambarsync
almalinuxalmalinux
archlinuxarch linux
gentoolinux
nixosnixos
novellsuse linux
tritondatacentersmartos
redhatenterprise linux

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • github.com/RsyncProject/rsync rsync

    • 3.2.7, 3.3.0affected

  • Red Hat Red Hat Enterprise Linux 10

    • 0:3.4.1-2.el10 and laternot affected · rpm

  • Red Hat Red Hat Enterprise Linux 6

    • all versionsunknown

  • Red Hat Red Hat Enterprise Linux 7

    • all versionsunknown

  • Red Hat Red Hat Enterprise Linux 8

    • all versionsunknown

  • Red Hat Red Hat Enterprise Linux 9

    • all versionsunknown

  • Red Hat Red Hat OpenShift Container Platform 4

    • all versionsunknown
    • all versionsunknown
Affected versions · NVD (10)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • almalinux almalinux10.0
  • archlinux arch linuxall versions
  • gentoo linuxall versions
  • nixos nixosbefore 24.11
  • nixos nixos24.11
  • novell suse linuxall versions
  • redhat enterprise linux10.0
  • samba rsync3.2.7
  • samba rsync3.3.0
  • tritondatacenter smartosbefore 20250123

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.18rsyncbefore 3.4.0-r03.4.0-r0
Debian:12rsyncbefore 3.2.7-1+deb12u13.2.7-1+deb12u1
Debian:13rsyncbefore 3.3.0+ds1-33.3.0+ds1-3
openSUSE:Leap 15.6rsyncbefore 3.2.7-150600.3.8.13.2.7-150600.3.8.1
openSUSE:Tumbleweedrsyncbefore 3.4.1-1.13.4.1-1.1
Red Hat:enterprise_linux:10.0rsyncbefore 0:3.4.1-2.el100:3.4.1-2.el10
Red Hat:enterprise_linux:10.0rsync-daemonbefore 0:3.4.1-2.el100:3.4.1-2.el10
Red Hat:enterprise_linux:10.0rsync-debuginfobefore 0:3.4.1-2.el100:3.4.1-2.el10
Red Hat:enterprise_linux:10.0rsync-debugsourcebefore 0:3.4.1-2.el100:3.4.1-2.el10
Red Hat:enterprise_linux:10.0rsync-rrsyncbefore 0:3.4.1-2.el100:3.4.1-2.el10
SUSE:Linux Enterprise Module for Basesystem 15 SP6rsyncbefore 3.2.7-150600.3.8.13.2.7-150600.3.8.1
SUSE:Linux Micro 6.0rsyncbefore 3.2.7-4.13.2.7-4.1
SUSE:Linux Micro 6.1rsyncbefore 3.3.0-slfo.1.1_3.13.3.0-slfo.1.1_3.1

Same product

samba: all records

Other highest-scoring records for the same primary product.

  • CVE-2017-16548The receive_xattr function in xattrs.c in rsync 3.1.2 and 3.1.3-development does not check for a trailing '\0' character in an xattr name…
    41Plan
  • CVE-2017-17434The daemon in rsync 3.1.2, and 3.1.3-development before 2017-12-03, does not check for fnamecmp filenames in the daemon_filter_list data…
    40Plan
  • CVE-2017-15994rsync 3.1.3-development before 2017-10-24 mishandles archaic checksums, which makes it easier for remote attackers to bypass intended…
    39Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2024-12087Jan 14, 2025 · Rsync: path traversal vulnerability in rsync
    31Monitor
  • ← EarlierCVE-2024-12088Jan 14, 2025 · Rsync: --safe-links option bypass leads to path traversal
    31Monitor
  • Later →CVE-2026-41035Apr 16, 2026 · In rsync 3.0.1 through 3.4.1, receive_xattr relies on an untrusted length value during a qsort call, leading to a receiver use-after-free.
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 rsync 3.2.7-1 on Azure Linux 3.03.4.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 rsync 3.4.1-1 on Azure Linux 3.03.4.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 rsync 3.2.5-1 on CBL Mariner 2.03.4.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 rsync 3.2.5-1 on CBL-Mariner 2.03.4.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 rsync 3.4.1-1 on CBL Mariner 2.03.4.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
alpine:rsync3.4.0-r0 · Alpine:v3.18Package registry (OSV)
debian:rsync3.2.7-1+deb12u1 · Debian:12Package registry (OSV)
opensuse:rsync3.2.7-150600.3.8.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:rsync0:3.4.1-2.el10 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:rsync-daemon0:3.4.1-2.el10 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:rsync-debuginfo0:3.4.1-2.el10 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:rsync-debugsource0:3.4.1-2.el10 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:rsync-rrsync0:3.4.1-2.el10 · Red Hat:enterprise_linux:10.0Package registry (OSV)
suse:rsync3.2.7-150600.3.8.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×3

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHub3 repositories2025-01-21 → 2025-11-24

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+5 d
  3. TodayNov 14, 2026+667 d

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-122 · Heap-based Buffer Overflow

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records