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.
CVE-2024-12084
“—” beside the score: it is equal to the CVSS score beside it.
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2025-01-15. A secondary CVSS source baseline 9.8; sources differ by 0.0.
Also known asEUVD-2024-50580 (ENISA EUVD) · GHSA-85h7-m8c3-v9wc (GitHub Security Advisories)Source: ENISA EUVD
- High exploitation likelihood — EPSS 73%
- Public exploit or proof-of-concept code is available
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8CRITICALmedium confidence
- EG Risk
- 88EG Risk 88/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity98% × 45%Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation73% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 73%
- EPSS %ILE
- 99th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 73% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
January 15, 2025
Last Modified
October 21, 2026
Advisory Details (8)
Auto-updated Oct 30, 2026RSync: Heap Buffer Overflow, Info Leak, Server Leaks, Path Traversal and Safe links Bypass · Advisory · google/security-research · GitHub
https://github.com/google/security-research/security/advisories/GHSA-p5pg-x43v-mvqjoss-security - Re: RSYNC: 6 vulnerabilities
http://www.openwall.com/lists/oss-security/2025/01/14/62330527 – (CVE-2024-12084) CVE-2024-12084 rsync: Heap Buffer Overflow in Rsync due to Improper Checksum Length Handling
https://bugzilla.redhat.com/show_bug.cgi?id=2330527CVE-2024-12084 - Red Hat Customer Portal
Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a
https://access.redhat.com/security/cve/CVE-2024-12084Affected: Red Hat Enterprise Linux 10.
https://access.redhat.com/errata/RHBA-2025:6470Vendor Advisories for CVE-2024-12084(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- patch-release-gitlab-18-1-2-releasedGitLab Security
GitLab Patch Release: 18.1.2, 18.0.4, 17.11.6
- RHBA-2025:6470Red Hat Product SecurityCritical
Red Hat Bug Fix Advisory: rsync bug fix and enhancement update
- CVE-2024-12084Microsoft Security Response Center (MSRC)Critical
Rsync: heap buffer overflow in rsync due to improper checksum length handling
Patch Availability(3)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | rsync (3.1.1-3ubuntu1.3+esm3) @ xenial | 2026-11-02 | ubuntu |
| ubuntu | rsync (3.3.0-1ubuntu0.1) @ oracular | 2026-11-02 | ubuntu |
| redhat | rsync-0:3.4.1-2.el10 | 2025-05-13 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(10 across 10 ecosystems)
Alpine:v3.18(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rsync | — |
| — |
Alpine:v3.19(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rsync | — |
| — |
Alpine:v3.20(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rsync | — |
| — |
Alpine:v3.21(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rsync | — |
| — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rsync | — |
| — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rsync | — |
| — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rsync | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rsync | 3.2.7-1 |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rsync | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rsync | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(2)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 28× in last 7d / 90× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 98 of 216 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 118 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 14:38 UTCEG score recompute
- 2026-11-02 14:38 UTCVendor advisory
- 2026-11-02 14:38 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-01 14:54 UTCEG score recompute
- 2026-11-01 14:54 UTCVendor advisory
- 2026-11-01 14:54 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-31 16:30 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-31 15:12 UTCEG score recompute
- 2026-10-31 15:12 UTCVendor advisory
- 2026-10-31 15:11 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-30 16:31 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-30 15:28 UTCEG score recompute
- 2026-10-30 15:28 UTCVendor advisory
- 2026-10-30 15:28 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-29 15:45 UTCEG score recompute
- 2026-10-29 15:45 UTCVendor advisory
- 2026-10-29 15:45 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-28 16:29 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-28 15:59 UTCEG score recompute
- 2026-10-28 15:59 UTCVendor advisory
- 2026-10-28 15:59 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-27 16:29 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-27 16:15 UTCEG score recompute
- 2026-10-27 16:15 UTCVendor advisory
- 2026-10-27 16:15 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 73 moreShow fewer
- 2026-10-26 16:29 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-26 16:22 UTCVendor advisory
- 2026-10-26 16:22 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-25 16:31 UTCEG score recompute
- 2026-10-25 16:31 UTCVendor advisory
- 2026-10-25 16:31 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-25 16:30 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-24 16:46 UTCEG score recompute
- 2026-10-24 16:46 UTCVendor advisory
- 2026-10-24 16:46 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-23 17:02 UTCEG score recompute
- 2026-10-23 17:02 UTCVendor advisory
- 2026-10-23 17:02 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-23 16:29 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-22 17:19 UTCEG score recompute
- 2026-10-22 17:19 UTCVendor advisory
- 2026-10-22 17:19 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-22 16:31 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-21 17:26 UTCEG score recompute
- 2026-10-21 17:26 UTCVendor advisory
- 2026-10-21 17:26 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-10-21 16:28 UTCEG score recompute
- 2026-10-21 16:28 UTCVendor advisory
- 2026-10-21 16:28 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-21 00:36 UTCEG score recompute
- 2026-10-21 00:36 UTCVendor advisory
- 2026-10-21 00:36 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-20 16:30 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-10-20 00:51 UTCEG score recompute
- 2026-10-20 00:51 UTCVendor advisory
- 2026-10-20 00:50 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-19 16:29 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-10-18 23:48 UTCEG score recompute
- 2026-10-18 23:48 UTCVendor advisory
- 2026-10-18 23:48 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-18 07:34 UTCEG score recompute
- 2026-10-18 00:03 UTCEG score recompute
- 2026-10-18 00:03 UTCVendor advisory
- 2026-10-18 00:02 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-17 16:30 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-10-17 00:18 UTCEG score recompute
- 2026-10-17 00:18 UTCVendor advisory
- 2026-10-17 00:18 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-15 23:45 UTCEG score recompute
- 2026-10-15 23:45 UTCVendor advisory
- 2026-10-15 23:45 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-15 16:29 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-10-14 16:30 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-10-14 15:23 UTCEG score recompute
- 2026-10-14 15:23 UTCVendor advisory
- 2026-10-14 15:23 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-13 16:30 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-10-13 14:48 UTCEG score recompute
- 2026-10-13 14:48 UTCVendor advisory
- 2026-10-13 14:48 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-12 15:05 UTCEG score recompute
- 2026-10-12 15:05 UTCVendor advisory
- 2026-10-12 15:05 UTCGHSA enrichmentGHSA-85h7-m8c3-v9wc · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-11 21:32 UTCEG score recompute
- 2026-10-11 13:45 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-10-10 19:58 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-10-08 17:07 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-10-07 23:46 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-10-06 15:15 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-10-03 01:25 UTCOSV refresh
- 2026-10-01 19:48 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-09-30 16:43 UTCEG score recompute
- 2026-09-30 15:01 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-09-27 13:43 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-09-26 00:23 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-09-24 14:01 UTCEPSS rescoreEPSS 72% · 99th percentile
Publicly available exploits
(1 reference)Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.
- Open source ↗GitHub PoCthemirze/cve-2024-12084Published Jan 21, 2025
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownAlpine:v3.18:rsync · Alpine:v3.19:rsync
Same vendor
5 shownredhat:RHBA-2025:6470
Frequently asked(5)
What is CVE-2024-12084?
When was CVE-2024-12084 made public?
Is CVE-2024-12084 actively exploited?
What is the CVSS score of CVE-2024-12084?
How do I remediate CVE-2024-12084?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-12084
Is Your Infrastructure Affected by CVE-2024-12084?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.