rsync 3.x before 3.0.8, when certain recursion, deletion, and ownership options are used, allows remote rsync servers to cause a denial of s
rsync 3.x before 3.0.8, when certain recursion, deletion, and ownership options are used, allows remote rsync servers to cause a denial of service (heap memory corruption and application crash) or possibly execute arbitrary code via malformed data.
- Published
- Mar 30, 2011
- Updated
- Jun 16, 2026
- EPSS
- 3.2% · 88th percentile
- CWE
- CWE-119
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 20 / 40 · 5.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.2%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; 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 helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| samba | rsync | cpe:2.3:a:samba:rsync |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- samba rsync3.0.0
- samba rsync3.0.1
- samba rsync3.0.2
- samba rsync3.0.3
- samba rsync3.0.4
- samba rsync3.0.5
- samba rsync3.0.6
- samba rsync3.0.7
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | rsync | before 3.0.8 | 3.0.8 |
| openSUSE:Tumbleweed | rsync | before 3.1.2-1.5 | 3.1.2-1.5 |
| Red Hat:enterprise_linux:6::client | rsync | before 0:3.0.6-5.el6_0.1 | 0:3.0.6-5.el6_0.1 |
| Red Hat:enterprise_linux:6::client | rsync-debuginfo | before 0:3.0.6-5.el6_0.1 | 0:3.0.6-5.el6_0.1 |
Same product
samba: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-12084Rsync: heap buffer overflow in rsync due to improper checksum length handling61This week
- 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
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 |
|---|---|---|
| debian:rsync | 3.0.8 · Debian:12 | Package registry (OSV) |
| opensuse:rsync | 3.1.2-1.5 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:rsync | 0:3.0.6-5.el6_0.1 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:rsync-debuginfo | 0:3.0.6-5.el6_0.1 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
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.
No credits in the CNA record.
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
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- High
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
AV:N/AC:H/Au:N/C:P/I:P/A:P
nvd-primary
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)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- gitweb.samba.org/?p=rsync.git%3Ba=commit%3Bh=83b94efa6b60a3ff5eee4c5f7812c617a90a03f6
- lists.fedoraproject.org/pipermail/package-announce/2011-April/057641.html
- lists.fedoraproject.org/pipermail/package-announce/2011-April/057736.html
- lists.fedoraproject.org/pipermail/package-announce/2011-April/057737.html
- lists.opensuse.org/opensuse-security-announce/2011-05/msg00005.html
- lists.samba.org/archive/rsync/2011-January/025988.html
- marc.info/?l=bugtraq&m=133226187115472&w=2
- rsync.samba.org/ftp/rsync/src/rsync-3.0.8-NEWS
- secunia.com/advisories/44071
- secunia.com/advisories/44088
- securitytracker.com/id?1025256
- www.mandriva.com/security/advisories?name=MDVSA-2011:066
- www.redhat.com/support/errata/RHSA-2011-0390.html
- www.vupen.com/english/advisories/2011/0792
- www.vupen.com/english/advisories/2011/0793
- www.vupen.com/english/advisories/2011/0873
- www.vupen.com/english/advisories/2011/0876
- bugzilla.redhat.com/show_bug.cgi?id=675036
- bugzilla.samba.org/show_bug.cgi?id=7936
Vendor advisories and official records. Exploit/PoC links are deliberately left out.