dbcve.org
ImagemagickApplication

CVE-2018-16328

CRITICAL · 9.8 CVSS v3.0 Published 2018-09-01
Fix available
A fix is available. Upgrade to 7.0.8-8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In ImageMagick before 7.0.8-8, a NULL pointer dereference exists in the CheckEventLogging function in MagickCore/log.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 confidence

A NULL pointer dereference vulnerability exists in the CheckEventLogging function in MagickCore/log.c in ImageMagick versions prior to 7.0.8-8. An attacker can trigger this by providing specially crafted input that causes the function to dereference a NULL pointer, potentially leading to denial of service or arbitrary code execution.

MitigationUpgrade ImageMagick to version 7.0.8-8 or later. If immediate upgrading is not feasible, disable or restrict the logging functionality in ImageMagick configurations as a temporary mitigation.

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
ImagemagickApplication
Affected:< 7.0.8-8

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed ImageMagick version
    Run 'identify -version' or 'convert -version' to display the installed ImageMagick version number
    Affected if The reported version is earlier than 7.0.8-8 (for example, 7.0.8-7, 7.0.7-x, or 6.x.x)
  2. Confirm logging is enabled in ImageMagick
    Check the ImageMagick configuration files (typically /etc/ImageMagick-6/ or /etc/ImageMagick/) for any Log settings, or run 'identify -list Configure' and look for LOG dependencies
    Affected if Logging functionality is compiled into the binary or enabled in the configuration, as the vulnerability exists in the CheckEventLogging function
  3. Verify the vulnerable log.c file is present
    Locate the MagickCore/log.c source file or compiled log.o object file within the ImageMagick installation directory structure
    Affected if The CheckEventLogging function exists in the installed build, indicating the vulnerable code path is present

The environment is affected if ImageMagick version is earlier than 7.0.8-8 and the logging component (containing CheckEventLogging) is present and enabled in the installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 7.0.8-8 or later
Fixed in 7.0.8-8
Interim mitigation

Upgrade ImageMagick to version 7.0.8-8 or later. If immediate upgrading is not feasible, disable or restrict the logging functionality in ImageMagick configurations as a temporary mitigation.

Recommended fix High confidence

ImageMagick 7.0.8-8 or later

  1. Identify your current ImageMagick version using 'convert -version' or 'magick -version'
  2. For Debian/Ubuntu-based systems: Run 'sudo apt-get update' then 'sudo apt-get install imagemagick' to install the latest available version
  3. For RHEL/CentOS/Fedora-based systems: Run 'sudo yum update ImageMagick' or 'sudo dnf update ImageMagick'
  4. For macOS with Homebrew: Run 'brew upgrade imagemagick'
  5. For source compilation: Download ImageMagick 7.0.8-8 or later from https://www.imagemagick.org/download/releases/
  6. After upgrading, verify the new version with 'convert -version' to confirm the fix is applied
  7. Test critical ImageMagick workflows to ensure functionality remains intact
Caveat Minimal risk - this is a security patch release; however, test workflows as minor behavior changes between patch versions are possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Imagemagick Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-16328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-16328 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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