VYPR
← All advisories
Unrated severityNVD Advisory· Published Jun 26, 2019· Updated Aug 4, 2024

CVE-2019-12975

CVE-2019-12975

Description

ImageMagick 7.0.8-34 has a memory leak in WriteDPXImage due to incomplete cleanup on write failure.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

ImageMagick 7.0.8-34 has a memory leak in WriteDPXImage due to incomplete cleanup on write failure.

Vulnerability

ImageMagick 7.0.8-34 (and possibly earlier) contains a memory leak in WriteDPXImage within coders/dpx.c. The bug occurs when a write operation fails after pixel allocation: the loop breaks early but DestroyQuantumInfo and CloseBlob are only called after the loop, leaving allocated pixels memory unreleased. Affected versions include 7.0.8-34; the issue was reported via GitHub issue #1517.

Exploitation

An attacker needs no special access; any user invoking ImageMagick's DPX writing (e.g., via convert or API) on a crafted image can trigger the leak. The failure condition arises when WriteBlob returns a count not equal to extent, causing an early loop exit. No race window or authentication required.

Impact

The memory leak gradually consumes heap, potentially leading to denial of service in long-running processes. No other CIA impact; privilege level remains unchanged.

Mitigation

A fix was committed in commit f1cc2e (see [1]). Users should upgrade to ImageMagick 7.0.8-35 or later. If unable to upgrade, monitor memory usage and limit DPX processing of untrusted images as a workaround.

References
  1. Possible but rare memory leak in function WriteDPXImage

AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

13

Patches

0

No patches discovered yet.

Vulnerability mechanics

Root cause

"The WriteDPXImage function fails to properly handle error conditions during the image writing loop, leading to a memory leak."

Attack vector

An attacker can trigger this vulnerability by providing a malformed image file that causes the WriteDPXImage function to exit the processing loop prematurely [ref_id=1]. When the loop breaks due to an error, the function fails to throw an exception, resulting in leaked memory [ref_id=1].

Affected code

The vulnerability is located in the WriteDPXImage function within the coders/dpx.c file [ref_id=1].

What the fix does

The advisory suggests that the function should explicitly call ThrowWriterException when the loop terminates before processing all image rows [ref_id=1]. This ensures that error states are properly handled and resources are cleaned up. The advisory notes that commit f1cc2eb provides the specific implementation details for this fix [ref_id=1].

Preconditions

  • inputThe attacker must provide a specially crafted image file that triggers a failure during the WriteDPXImage processing loop.

Generated on Jun 1, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

5

News mentions

0

No linked articles in our index yet.