CVE-2018-19567
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA floating point exception 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA floating point exception (likely divide-by-zero or overflow) occurs in the parse_tiff_ifd function of dcraw when processing specially crafted malicious TIFF files. Attackers can trigger this condition to cause a denial of service by crashing any application that bundles the vulnerable dcraw code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 9.28CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if dcraw is installedRun 'dcraw' or 'dcraw -v' from command line to check if the program exists and retrieve its version informationAffected if dcraw is present and version is 9.28 or lower
-
Determine the exact dcraw versionCheck the application's version string or binary metadata; common methods include 'dcraw -v' output, dpkg/rpm package queries, or inspecting the binary file informationAffected if Version is 9.28 or any version lower than 9.29
-
Identify applications bundling dcraw codeSearch application dependencies or binaries for references to dcraw, libdcraw, or the parse_tiff_ifd function; review application components that handle image processingAffected if Any application bundles or links to dcraw version 9.28 or lower and processes TIFF files
-
Verify TIFF processing capabilityCheck if any application or script uses dcraw to decode or process TIFF image files, particularly from untrusted sourcesAffected if dcraw is used to process TIFF files, especially those from external or untrusted sources
-
Confirm parse_tiff_ifd function is presentIf performing binary analysis, search the dcraw binary or library for the parse_tiff_ifd function symbol; examine the source code if availableAffected if The parse_tiff_ifd function exists in the deployed dcraw code
A user is affected if dcraw version 9.28 or lower is installed and is used to process TIFF files, particularly from untrusted or external sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate dcraw to version 9.29 or later which contains the fix, or implement input validation in parse_tiff_ifd to check for zero/negative values before performing floating-point operations on TIFF IFD tag data.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19567 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-19567 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data