ImageMagick has memory leak of watermark Image object in ReadSTEGANOImage on multiple error/early-return pathsGHSA-g2pr-qxjg-7r2w
MEDIUMFix: ImageMagick/ImageMagick@93ad259GHSA-g2pr-qxjg-7r2w is a medium-severity (CVSS 5.3) CWE-401 vulnerability in Magick.NET-Q16-AnyCPU. A fix is available for Magick.NET-Q16-AnyCPU — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-g2pr-qxjg-7r2w.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
Magick.NET-Q16-AnyCPU.NETMagick.NET-Q16-HDRI-AnyCPU.NETMagick.NET-Q16-HDRI-OpenMP-arm64.NETMagick.NET-Q16-HDRI-OpenMP-x64.NETMagick.NET-Q16-HDRI-arm64.NETMagick.NET-Q16-HDRI-x64.NETMagick.NET-Q16-HDRI-x86.NETMagick.NET-Q16-OpenMP-arm64+10 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Summary
In ReadSTEGANOImage() (coders/stegano.c), the watermark Image object is not freed on three early-return paths, resulting in a definite memory leak (~13.5KB+ per invocation) that can be exploited for denial of service.
Direct leak of 13512 byte(s) in 1 object(s) allocated from:
#0 0x7f5c11e27887 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145
#1 0x55cdc38f65c4 in AcquireMagickMemory MagickCore/memory.c:536
#2 0x55cdc38f65eb in AcquireCriticalMemory MagickCore/memory.c:612
#3 0x55cdc3899e91 in AcquireImage MagickCore/image.c:154
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Magick.NET-Q16-AnyCPU | all versions | 14.10.3dotnet add package Magick.NET-Q16-AnyCPU --version 14.10.3 |
| .NETNuGet | Magick.NET-Q16-HDRI-AnyCPU | all versions | 14.10.3dotnet add package Magick.NET-Q16-HDRI-AnyCPU --version 14.10.3 |
| .NETNuGet | Magick.NET-Q16-HDRI-OpenMP-arm64 | all versions | 14.10.3dotnet add package Magick.NET-Q16-HDRI-OpenMP-arm64 --version 14.10.3 |
| .NETNuGet | Magick.NET-Q16-HDRI-OpenMP-x64 | all versions | 14.10.3dotnet add package Magick.NET-Q16-HDRI-OpenMP-x64 --version 14.10.3 |
| .NETNuGet | Magick.NET-Q16-HDRI-arm64 | all versions | 14.10.3dotnet add package Magick.NET-Q16-HDRI-arm64 --version 14.10.3 |
| .NETNuGet | Magick.NET-Q16-HDRI-x64 | all versions | 14.10.3dotnet add package Magick.NET-Q16-HDRI-x64 --version 14.10.3 |
Affected Products
imagemagickimagemagickDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Magick.NET-Q16-AnyCPU, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Magick.NET-Q16-AnyCPU to 14.10.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g2pr-qxjg-7r2w is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This MODERATE impact vulnerability in ImageMagick involves a memory leak when processing certain image files due to unfreed objects in the `ReadSTEGANOImage()` function. This flaw can lead to a denial of service by exhausting system memory. Red Hat Enterprise Linux and community projects utilizing ImageMagick are…
To mitigate this issue, avoid processing untrusted or maliciously crafted image files with ImageMagick. If ImageMagick is used in a server-side application or service that handles external input, consider implementing resource limits for the ImageMagick process to prevent excessive memory consumption, or run the process within a sandboxed environment to contain potential denial of service attacks.Source: Red Hat security advisory for GHSA-g2pr-qxjg-7r2w (CC BY 4.0)
Frequently Asked Questions
Is GHSA-g2pr-qxjg-7r2w in your dependencies?
Find it across NuGet, including transitive dependencies.