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. The victim must run rsync with -X (aka --xattrs). On Linux, many (but not all) common configurations are vulnerable. Non-Linux platforms are...
Product
cbl-mariner rsync vulnerabilities
9 published CVES affecting cbl-mariner rsync, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 9
- Critical
- 2
- High
- 4
- Medium
- 3
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest cbl-mariner rsync CVEs
Newest publication first
-
HighCVSS 7.8 EPSS 0.41%
-
CriticalCVSS 9.8 EPSS 0.76%
Perl versions from 5.9.4 before 5.40.4-RC1, from 5.41.0 before 5.42.2-RC1, from 5.43.0 before 5.43.9 contain a vulnerable version of Compress::Raw::Zlib. Compress::Raw::Zlib is included in the Perl package as a dual-life core module, and is vulnerable to CVE-2026-3381 due to a ve...
-
MediumCVSS 4.3 EPSS 0.35%
A malicious client acting as the receiver of an rsync file transfer can trigger an out of bounds read of a heap based buffer, via a negative array index. The malicious rsync client requires at least read access to the remote rsync module in order to trigger the issue.
-
CVE-2024-12084 Rsync: heap buffer overflow in rsync due to improper checksum length handling
PublishedCriticalCVSS 9.8 EPSS 72.5%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 buf...
-
HighCVSS 7.5 EPSS 2.3%
A path traversal vulnerability exists in rsync. It stems from behavior enabled by the --inc-recursive option, a default-enabled option for many client options and can be enabled by the server even if not explicitly enabled by the client. When using the --inc-recursive option, a l...
-
MediumCVSS 5.6 EPSS 0.39%
A flaw was found in rsync. This vulnerability arises from a race condition during rsync's handling of symbolic links. Rsync's default behavior when encountering symbolic links is to skip them. If an attacker replaced a regular file with a symbolic link at the right time, it was p...
-
HighCVSS 7.5 EPSS 4.6%
A flaw was found in rsync. When using the --safe-links option, the rsync client fails to properly verify if a symbolic link destination sent from the server contains another symbolic link within it. This results in a path traversal vulnerability, which may lead to arbitrary file...
-
MediumCVSS 6.8 EPSS 1.8%
A flaw was found in rsync. It could allow a server to enumerate the contents of an arbitrary file from the client's machine. This issue occurs when files are being copied from a client to a server. During this process, the rsync server will send checksums of local data to the cli...
-
HighCVSS 7.5 EPSS 8.6%
A flaw was found in rsync which could be triggered when rsync compares file checksums. This flaw allows an attacker to manipulate the checksum length (s2length) to cause a comparison between a checksum and uninitialized memory and leak one byte of uninitialized stack data at a ti...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.