CVE-2014-8242

Updated librsync packages fix security vulnerability:

librsync before 1.0.0 used a truncated MD4 "strong" check sum to match blocks. However, MD4 is not cryptographically strong. It's possible that an attacker who can control the contents of one part of a file could use it to control other regions of the file, if it's transferred using librsync/rdiff (CVE-2014-8242).

The change to fix this is not backward compatible with older versions of librsync. Backward compatibility can be obtained using the new rdiff sig --hash=md4 option or through specifying the "signature magic" in the API, but this should not be used when either the old or new file contain untrusted data.

Also, any applications that use the librsync library will need to be recompiled against the updated library. The duplicity and rdiff-backup packages have been rebuilt for this reason.

These are all security issues fixed in the librsync-devel-1.0.0-2.8 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the rsync-3.1.2-1.5 package on the GA media of openSUSE Tumbleweed.

This update for rsync fixes two security issues and two non-security bugs.

The following vulnerabilities were fixed:

• CVE-2014-8242: Checksum collisions leading to a denial of service (bsc#900914)
• CVE-2014-9512: Malicious servers could send files outside of the transferred directory (bsc#915410)

The following non-security bugs were fixed:

• bsc#922710: Prevent rsyncd from spamming the log when trying to register SLP.
• bsc#898513: slp support broke rsync usage.

This update for rsync fixes two security issues:

• CVE-2014-8242: Checksum collisions leading to a denial of service (bsc#900914)
• CVE-2014-9512: Malicious servers could send files outside of the transferred directory (bsc#915410)

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.