High severity · published May 27, 2021
CVE-2020-14387
A flaw was found in rsync in versions since 3.2.0pre1
7.4
CVSS
1.1%
EPSS
No
On KEV
Description
A flaw was found in rsync in versions since 3.2.0pre1. Rsync improperly validates certificate with host mismatch vulnerability. A remote, unauthenticated attacker could exploit the flaw by performing a man-in-the-middle attack using a valid certificate for another hostname which could compromise confidentiality and integrity of data transmitted using rsync-ssl. The highest threat from this vulnerability is to data confidentiality and integrity. This flaw affects rsync versions before 3.2.4.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)1.1% · higher than 66% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
RS
Rsync · Samba
3.2.1 before 3.2.4; 3.2.0; 3.2.0; 3.2.0; 3.2.0 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2020-14387
CVE.org
https://www.cve.org/CVERecord?id=CVE-2020-14387
Issue Tracking
https://bugzilla.redhat.com/show_bug.cgi?id=1875549
More from Rsync
9.8
CVE-2024-12084
Rsync: heap buffer overflow in rsync due to improper checksum length handling
9.8
CVE-2017-17434
The 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 structure (in the recv_files function in…
9.8
CVE-2017-16548
The 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, which allows remote attackers to cause a…
9.8
CVE-2017-15994
rsync 3.1.3-development before 2017-10-24 mishandles archaic checksums, which makes it easier for remote attackers to bypass intended access restrictions
9.1
CVE-2026-53791
rsync < 3.5.0 Daemon IP Spoofing via PROXY Protocol Header