LiveActive security incident?Get immediate response
CVE Record

CVE-2017-14175: In coders/xbm.c in ImageMagick 7.0.6-1 Q16, a DoS in ReadXBMImage() due to lack of an EOF (End of File) che...

In coders/xbm.c in ImageMagick 7.0.6-1 Q16, a DoS in ReadXBMImage() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted XBM file, which claims large rows and columns fields in the header but does not contain sufficient backing data, is provided, the loop over the rows would consume huge CPU resources, since there is no EOF check inside the loop.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-14175 is a denial-of-service flaw in ImageMagick’s XBM image parser. A specially crafted XBM file can cause excessive CPU use during image reading, potentially slowing or exhausting systems that process untrusted images.

Executive priority

Treat this as a practical availability risk, not a confirmed remote code execution issue. Prioritize internet-facing or business-critical image-processing services, especially where users can submit files.

Technical view

The source describes missing EOF handling in coders/xbm.c ReadXBMImage() in ImageMagick 7.0.6-1 Q16. An XBM header can claim large dimensions without enough backing data, causing row-processing loops to consume substantial CPU.

Likely exposure

Exposure is most likely where ImageMagick processes user-supplied or externally sourced XBM images, including upload, thumbnailing, conversion, or batch-processing services. The bundle does not identify broader affected version ranges beyond the cited ImageMagick 7.0.6-1 Q16 context.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Public issue and vendor advisories indicate the weakness was disclosed and addressed through ImageMagick and distribution security updates.

Researcher notes

Evidence supports a CPU-consumption DoS in the XBM decoder caused by insufficient EOF checks. Severity scoring, complete affected-version range, and exploitation-in-the-wild evidence are not provided in the bundle.

Mitigation direction

  • Apply ImageMagick security updates from the relevant OS or package vendor.
  • Verify whether deployed packages include the upstream fix commit or vendor backport.
  • Review ImageMagick guidance before assuming unsupported versions are fixed.
  • Reduce exposure of services that process untrusted XBM files until updated.

Validation and detection

  • Inventory systems and applications that call ImageMagick for image parsing or conversion.
  • Check installed ImageMagick package versions against Ubuntu, Gentoo, Debian, or upstream guidance.
  • Confirm vendor changelogs or package metadata reference CVE-2017-14175 or the fix.
  • Identify upload and conversion paths that accept XBM or untrusted image content.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-14175 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.