Current Description

librsync before 1.0.0 uses a truncated MD4 checksum to match blocks, which makes it easier for remote attackers to modify transmitted data via a birthday attack.

Basic Data

PublishedOctober 26, 2015
Last ModifiedMay 19, 2020
Data TypeCVE
Data FormatMITRE
Data Version4.0
Problem TypeCWE-310
CVE Data Version4.0

Base Metric V2

CVSS 2 - Version2.0
CVSS 2 - Vector StringAV:N/AC:M/Au:N/C:N/I:P/A:P
CVSS 2 - Access VectorNETWORK
CVSS 2 - Access ComplexityMEDIUM
CVSS 2 - AuthenticationNONE
CVSS 2 - Confidentiality ImpactNONE
CVSS 2 - Availability ImpactPARTIAL
CVSS 2 - Base Score5.8
Exploitability Score8.6
Impact Score4.9
Obtain All Privilegefalse
Obtain User Privilegefalse
Obtain Other Privilegefalse

Base Metric V3

No data provided.


  • OR - Configuration 1
    Cpe VersionPartVendorProductVersionUpdateEditionLanguageSW EditionTarget SWTarget HWOtherVersion Start IncludingVersion End IncludingVersion Start ExcludingVersion End Excluding
    2.3ApplicationLibrsync ProjectLibrsync********1.0.0

Vulnerable Software List

Librsync Project Librsync *


FEDORA-2015-2923 List Third Party Advisory
FEDORA-2015-3366 List Third Party Advisory
FEDORA-2015-3497 List Third Party Advisory
openSUSE-SU-2015:1752 List Third Party Advisory
[oss-security] 20140728 rsync vulnerable to collisions List Third Party Advisory
[oss-security] 20140805 [CVE Requests] rsync and librsync collisions List Third Party Advisory
[oss-security] 20141012 Re: [CVE Requests] rsync and librsync collisions List Third Party Advisory Tracking Third Party Advisory Third Party Advisory Third Party Advisory
GLSA-201605-04 Party Advisory Party Advisory