CVE-2018-6930
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 stack-based buffer over-read in the ComputeResizeImage function in the MagickCore/accelerate.c file of ImageMagick 7.0.7-22 allows a remote attacker to cause a denial of service (application crash) via a maliciously crafted pict file.
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 confidenceA stack-based buffer over-read vulnerability exists in ImageMagick 7.0.7-22 within the ComputeResizeImage function in MagickCore/accelerate.c. The vulnerability is triggered when processing a maliciously crafted .pict image file, causing the application to read beyond buffer boundaries and crash, resulting in denial of service.
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= 7.0.7-22CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/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.
-
Check installed ImageMagick versionRun 'convert --version' or 'identify --version' to display the installed ImageMagick version numberAffected if The displayed version is exactly 7.0.7-22
-
Confirm ImageMagick binary locationRun 'which convert' or 'which identify' to locate the binary being used, as multiple installations may existAffected if The binary reports version 7.0.7-22 regardless of path
-
Check if .pict format support is enabledRun 'convert -list format' and look for 'PICT' or 'Pict' in the output to see if PICT format decoding is availableAffected if PICT format is listed as supported (readable) in the format list
-
Verify accelerate module is in useCheck if MagickCore/accelerate.c functionality is loaded - this is typically built into the core library; confirm by reviewing 'identify -list configure' output for module pathsAffected if The ImageMagick installation includes the accelerate component from MagickCore/accelerate.c
-
Test PICT file processing capabilityAttempt to identify a dummy or test .pict file with 'identify input.pict' to confirm the decoder is functionalAffected if The command processes the .pict file without error, indicating the vulnerable code path is reachable
You are affected if ImageMagick version 7.0.7-22 is installed AND the PICT image format decoder is enabled and usable in your environment.
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 ImageMagick to a version newer than 7.0.7-22 that contains the patch for this vulnerability. Alternatively, validate and reject .pict files at input processing boundaries if immediate patching is not feasible.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6930 — 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-6930 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