dbcve.org
ImagemagickApplication

CVE-2022-1114

HIGH · 7.1 CVSS v3.1 Published 2022-04-29
Fix available
A fix is available. Upgrade to 6.9.12-43 / 7.1.0-28 or later.
See remediation →
74/100
Remediation priority · Elevated
No privileges

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
A heap-use-after-free flaw was found in ImageMagick's RelinquishDCMInfo() function of dcm.c file. This vulnerability is triggered when an attacker passes a specially crafted DICOM image file to ImageMagick for conversion, potentially leading to information disclosure and a denial of service.

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 confidence

A heap-use-after-free vulnerability exists in ImageMagick's RelinquishDCMInfo() function in dcm.c. When processing a specially crafted DICOM image file, memory is freed but then accessed again, leading to potential information disclosure and denial of service.

MitigationUpdate ImageMagick to the patched version; avoid processing untrusted DICOM files until patched; implement input validation for DICOM files.

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:>= 6.0, < 6.9.12-43>= 7.0.0-0, < 7.1.0-28

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

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

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

  1. Identify ImageMagick installation
    Run 'convert --version' or 'magick --version' to see if ImageMagick is installed and get the version number
    Affected if ImageMagick is installed with a version matching the affected ranges (< 6.9.12-43 for 6.x, or < 7.1.0-28 for 7.x)
  2. Confirm DICOM file support is enabled
    Run 'convert -list configure | grep -i dcm' or check for dcm.c module presence in the ImageMagick installation directory
    Affected if DICOM support (dcm.c/dcm module) is compiled and available in the ImageMagick build
  3. Identify DICOM file processing workflows
    Review application logs, scripts, or automation that invoke ImageMagick to process .dcm or .dicom files
    Affected if ImageMagick is used to process DICOM files from untrusted sources
  4. Check for recent processing of DICOM files
    Examine log files or image processing directories for recent .dcm file activity using 'find . -name "*.dcm" -mtime -30' or similar
    Affected if DICOM files have been recently processed by ImageMagick

You are affected if ImageMagick is installed with a vulnerable version (6.x < 6.9.12-43 or 7.x < 7.1.0-28) AND DICOM support is enabled AND your environment processes DICOM files.

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 6.9.12-43 / 7.1.0-28 or later
Fixed in 6.9.12-437.1.0-28
Interim mitigation

Update ImageMagick to the patched version; avoid processing untrusted DICOM files until patched; implement input validation for DICOM files.

Recommended fix High confidence

ImageMagick 6.9.12-43 or later (6.x branch); ImageMagick 7.1.0-28 or later (7.x branch)

  1. Check current ImageMagick version by running 'convert -version' or 'magick -version'
  2. Update your system's package repository metadata
  3. Install the updated ImageMagick package using your system's package manager (e.g., 'apt-get update && apt-get upgrade' for Debian/Ubuntu, 'yum update' for RHEL/CentOS, 'dnf update' for Fedora)
  4. Verify the updated version matches or exceeds the fixed release (6.9.12-43 for 6.x branch or 7.1.0-28 for 7.x branch)
  5. Restart any services or applications that use ImageMagick to ensure the patched version is loaded

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1114 — 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-2022-1114 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