Rsync: heap buffer overflow in rsync due to improper checksum length handling
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
- Jun 29, 2026
- EPSS
- 72.1% · 99th percentile
- CWE
- CWE-122
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
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.1%
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.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| samba | rsync | cpe:2.3:a:samba:rsync |
| almalinux | almalinux | cpe:2.3:o:almalinux:almalinux |
| archlinux | arch linux | cpe:2.3:o:archlinux:arch_linux |
| gentoo | linux | cpe:2.3:o:gentoo:linux |
| nixos | nixos | cpe:2.3:o:nixos:nixos |
| novell | suse linux | cpe:2.3:o:novell:suse_linux |
| tritondatacenter | smartos | cpe:2.3:o:tritondatacenter:smartos |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
Affected versions
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
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
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.18 | rsync | before 3.4.0-r0 | 3.4.0-r0 |
| Debian:12 | rsync | before 3.2.7-1+deb12u1 | 3.2.7-1+deb12u1 |
| Debian:13 | rsync | before 3.3.0+ds1-3 | 3.3.0+ds1-3 |
| openSUSE:Tumbleweed | rsync | before 3.4.1-1.1 | 3.4.1-1.1 |
| Red Hat:enterprise_linux:10.0 | rsync | before 0:3.4.1-2.el10 | 0:3.4.1-2.el10 |
| Red Hat:enterprise_linux:10.0 | rsync-daemon | before 0:3.4.1-2.el10 | 0:3.4.1-2.el10 |
| Red Hat:enterprise_linux:10.0 | rsync-debuginfo | before 0:3.4.1-2.el10 | 0:3.4.1-2.el10 |
| Red Hat:enterprise_linux:10.0 | rsync-debugsource | before 0:3.4.1-2.el10 | 0:3.4.1-2.el10 |
| Red Hat:enterprise_linux:10.0 | rsync-rrsync | before 0:3.4.1-2.el10 | 0:3.4.1-2.el10 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | rsync | before 3.2.7-150600.3.8.1 | 3.2.7-150600.3.8.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | rsync | before 3.2.7-150600.3.8.1 | 3.2.7-150600.3.8.1 |
| SUSE:Linux Micro 6.0 | rsync | before 3.2.7-4.1 | 3.2.7-4.1 |
| SUSE:Linux Micro 6.1 | rsync | before 3.3.0-slfo.1.1_3.1 | 3.3.0-slfo.1.1_3.1 |
Same product
samba: all recordsOther 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, w41Plan
- 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 str40Plan
- CVE-2017-15994rsync 3.1.3-development before 2017-10-24 mishandles archaic checksums, which makes it easier for remote attackers to bypass intended access39Monitor
- CVE-2026-53791rsync < 3.5.0 Daemon IP Spoofing via PROXY Protocol Header36Monitor
- CVE-2026-70461rsync 3.2.5 < 3.5.0 Heap Out-of-Bounds Write via files-from Entry35Monitor
- CVE-2026-70463rsync 3.1.0 < 3.5.0 Authorization Bypass via auth users Directive Parsing34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Alpine:rsync | 3.4.0-r0 · Alpine:v3.18 | Package registry (OSV) |
| Debian:rsync | 3.2.7-1+deb12u1 · Debian:12 | Package registry (OSV) |
| openSUSE:rsync | 3.2.7-150600.3.8.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| Red Hat:rsync | 0:3.4.1-2.el10 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| Red Hat:rsync-daemon | 0:3.4.1-2.el10 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| Red Hat:rsync-debuginfo | 0:3.4.1-2.el10 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| Red Hat:rsync-debugsource | 0:3.4.1-2.el10 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| Red Hat:rsync-rrsync | 0:3.4.1-2.el10 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| SUSE:rsync | 3.2.7-150600.3.8.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package 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.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:4 | 2025-01-21 |
| Proof-of-concept repository on GitHub | stars:1 | 2025-01-29 |
| Proof-of-concept repository on GitHub | stars:1 | 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.
- Published
- First PoC+6 d
- TodaySep 29, 2026+622 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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 OverflowCVSS 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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- access.redhat.com/errata/RHBA-2025:6470
- access.redhat.com/security/cve/CVE-2024-12084
- bugzilla.redhat.com/show_bug.cgi?id=2330527
- kb.cert.org/vuls/id/952657
- www.openwall.com/lists/oss-security/2025/01/14/6
- security.netapp.com/advisory/ntap-20250131-0002/
- www.kb.cert.org/vuls/id/952657
Vendor advisories and official records. Exploit/PoC links are deliberately left out.