Skip to content
Fencer Intel
medium 5.8

CVE-2014-8242 json

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

published 11y ago modified 4mo ago also EUVD-2014-8083

cvss
5.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.9%
EPSS 2.9% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

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.

Patch / fix

  • librsync_project librsync 1.0.0
  • librsync Debian 14, Debian 13, Debian 12 2.0.2-1

debian advisories DEBIAN-CVE-2014-8242

  • rsync SLES for SAP 11 SP4, SLES for SAP 11 SP3, SLES 11 SP4 +4 more 3.0.4-2.49.1
  • rsync SLES for SAP 12 SP1, SLES for SAP 12, SLES 12 SP1 +3 more 3.1.0-6.1

suse advisories SUSE-SU-2016:0176-1SUSE-SU-2016:0173-1

  • librsync openSUSE Tumbleweed 1.0.0-2.8
  • rsync openSUSE Tumbleweed 3.1.2-1.5

opensuse advisories openSUSE-SU-2024:10257-1openSUSE-SU-2024:10548-1

Is CVE-2014-8242 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-8242 updated cvss 4.0

librsync: MD4 collision file corruption

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.94% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:N/I:P/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.