MGASA-2015-0146

Source
https://advisories.mageia.org/MGASA-2015-0146.html
Import Source
https://advisories.mageia.org/MGASA-2015-0146.json
JSON Data
https://api.test.osv.dev/v1/vulns/MGASA-2015-0146
Related
Published
2015-04-15T09:01:28Z
Modified
2015-04-15T08:47:03Z
Summary
Updated librsync packages fix security vulnerabilities
Details

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.

References
Credits

Affected packages

Mageia:4 / librsync

Package

Name
librsync
Purl
pkg:rpm/mageia/librsync?distro=mageia-4

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.0.0-2.2.mga4

Ecosystem specific

{
    "section": "core"
}

Mageia:4 / duplicity

Package

Name
duplicity
Purl
pkg:rpm/mageia/duplicity?distro=mageia-4

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.6.22-5.1.mga4

Ecosystem specific

{
    "section": "core"
}

Mageia:4 / rdiff-backup

Package

Name
rdiff-backup
Purl
pkg:rpm/mageia/rdiff-backup?distro=mageia-4

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.3.3-8.1.mga4

Ecosystem specific

{
    "section": "core"
}