CVE-2018-10804
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 · uneditedImageMagick version 7.0.7-28 contains a memory leak in WriteTIFFImage in coders/tiff.c.
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 · high confidenceImageMagick version 7.0.7-28 contains a memory leak in the WriteTIFFImage function within coders/tiff.c. The vulnerability stems from improper memory management when writing TIFF format images, causing resource exhaustion over repeated operations.
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= 14.04= 16.04= 17.10= 18.04= 7.0.7-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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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.
-
Check installed ImageMagick versionRun `convert --version` or `magick --version` to see the installed version numberAffected if Version is exactly 7.0.7-28 (the specific affected version)
-
Confirm TIFF support is enabledRun `convert -list configure | grep -i tiff` or check if TIFF coders are present in the ImageMagick configurationAffected if TIFF support is compiled/enabled (the vulnerability is in the WriteTIFFImage function)
-
Identify TIFF write operations in useReview application logs or image processing scripts to see if images are being written in TIFF format using ImageMagickAffected if The system writes TIFF images using ImageMagick, triggering the vulnerable WriteTIFFImage code path
-
Check Ubuntu package version if installed via aptRun `dpkg -l | grep imagemagick` on Ubuntu/Debian systems to get the exact package versionAffected if Package version matches 7.0.7-28 from the affected Ubuntu releases (14.04, 16.04, 17.10, 18.04)
You are affected if ImageMagick version 7.0.7-28 is installed AND the system processes or writes TIFF format images.
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 dataUpgrade ImageMagick to a version newer than 7.0.7-28 that contains the patched code, or apply the specific patch addressing the memory leak in WriteTIFFImage.
- 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-10804 — 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-10804 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