Skip to content
Fencer Intel
high 7.1

CVE-2018-19566 json

A heap buffer over-read in parse_tiff_ifd in dcraw through 9.28 could be used by attackers able to supply malicious files to crash an appli…

published 7y ago modified 4mo ago also EUVD-2018-11255

cvss
7.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits
0
none known

Summary

A heap buffer over-read in parse_tiff_ifd in dcraw through 9.28 could be used by attackers able to supply malicious files to crash an application that bundles the dcraw code or leak private information.

Patch / fix

  • dcraw SLE Workstation Extension 12 SP5, SLE Software Development Kit 12 SP5 9.28.0-3.3.1
  • dcraw openSUSE Leap 15.3 9.28.0-150000.3.3.1

suse advisories SUSE-SU-2022:1749-1SUSE-SU-2022:1277-1

  • dcraw openSUSE Tumbleweed 9.28.0-2.1

opensuse advisories openSUSE-SU-2024:11997-1

Is CVE-2018-19566 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-2018-19566 updated cvss 4.4

dcraw: Heap buffer over-read in parse_tiff_ifd resulting in a denial of service or information leak

  • Red Hat Enterprise Linux 5 dcraw Red Hat Enterprise Linux 6 dcraw
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 7 dcraw Red Hat Enterprise Linux 8 dcraw
    affected: no fix available “Fix deferred”

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

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

CVSS scores

assigned by version score vector
NVD 3.0 7.1 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:N/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.