Skip to content

GHSA-cfh4-9f7v-fhrc CVE-2025-53019

ImageMagick has a Memory Leak in magick stream

High NuGet
Severity
3.7 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.56%
Chance of exploitation in the next 30 days. Higher than 46.51% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-125 Out-of-bounds Read
CWE-401 Missing Release of Memory after Effective Lifetime
CWE-404 Improper Resource Shutdown or Release
Fix
Available
18 packages have a fixed version

Description

Summary

In ImageMagick's magick stream command, specifying multiple consecutive %d format specifiers in a filename template causes a memory leak.

Details

  • Vulnerability Type: Memory leak
  • Affected Version: ImageMagick 7.1.1-47 (as of commit 82572afc, June 2025)

Reproduction

Tested Environment

  • Operating System: Ubuntu 22.04 LTS
  • Architecture: x86_64
  • Compiler: gcc with AddressSanitizer (gcc version: 11.4.0)

Reproduction Steps

# Clone source
git clone --depth 1 --branch 7.1.1-47 https://github.com/ImageMagick/ImageMagick.git ImageMagick-7.1.1
cd ImageMagick-7.1.1

# Build with ASan
CFLAGS="-g -O0 -fsanitize=address -fno-omit-frame-pointer" CXXFLAGS="$CFLAGS" LDFLAGS="-fsanitize=address" ./configure --enable-maintainer-mode --enable-shared && make -j$(nproc) && make install

# Trigger crash
./utilities/magick stream %d%d a a

Output

$ magick stream %d%d a a
stream: no decode delegate for this image format `' @ error/constitute.c/ReadImage/746.
stream: missing an image filename `a' @ error/stream.c/StreamImageCommand/755.

=================================================================
==114==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 152 byte(s) in 1 object(s) allocated from:
    #0 0x7fc4ebe58887 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145
    #1 0x7fc4eb563c5c in AcquireMagickMemory MagickCore/memory.c:559
    #2 0x7fc4eb563c82 in AcquireCriticalMemory MagickCore/memory.c:635
    #3 0x7fc4eb60c2be in AcquireQuantumInfo MagickCore/quantum.c:119
    #4 0x7fc4eb6b6621 in StreamImage MagickCore/stream.c:1335
    #5 0x7fc4eb09d889 in StreamImageCommand MagickWand/stream.c:292
    #6 0x7fc4eaf1295d in MagickCommandGenesis MagickWand/magick-cli.c:177
    #7 0x55a34f7c0a0c in MagickMain utilities/magick.c:153
    #8 0x55a34f7c0cba in main utilities/magick.c:184
    #9 0x7fc4ea38fd8f in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58

Indirect leak of 64 byte(s) in 1 object(s) allocated from:
    #0 0x7fc4ebe5957c in __interceptor_posix_memalign ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:226
    #1 0x7fc4eb680e2f in AcquireSemaphoreMemory MagickCore/semaphore.c:154
    #2 0x7fc4eb680f30 in AcquireSemaphoreInfo MagickCore/semaphore.c:200
    #3 0x7fc4eb60d38d in GetQuantumInfo MagickCore/quantum.c:435
    #4 0x7fc4eb60c30e in AcquireQuantumInfo MagickCore/quantum.c:121
    #5 0x7fc4eb6b6621 in StreamImage MagickCore/stream.c:1335
    #6 0x7fc4eb09d889 in StreamImageCommand MagickWand/stream.c:292
    #7 0x7fc4eaf1295d in MagickCommandGenesis MagickWand/magick-cli.c:177
    #8 0x55a34f7c0a0c in MagickMain utilities/magick.c:153
    #9 0x55a34f7c0cba in main utilities/magick.c:184
    #10 0x7fc4ea38fd8f in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58

SUMMARY: AddressSanitizer: 216 byte(s) leaked in 2 allocation(s).

Commits

Fixed in https://github.com/ImageMagick/ImageMagick/commit/fc3ab0812edef903bbb2473c0ee652ddfd04fe5c and https://github.com/ImageMagick/ImageMagick6/commit/d49460522669232159c2269fa64f73ed30555c1b

Affected versions

NuGet

PackageVulnerableFixed in
Magick.NET-Q16-AnyCPU
< 14.7.0
14.7.0
Magick.NET-Q16-HDRI-AnyCPU
< 14.7.0
14.7.0
Magick.NET-Q16-HDRI-OpenMP-arm64
< 14.7.0
14.7.0
Magick.NET-Q16-HDRI-OpenMP-x64
< 14.7.0
14.7.0
Magick.NET-Q16-HDRI-arm64
< 14.7.0
14.7.0
Magick.NET-Q16-HDRI-x64
< 14.7.0
14.7.0
Magick.NET-Q16-HDRI-x86
< 14.7.0
14.7.0
Magick.NET-Q16-OpenMP-arm64
< 14.7.0
14.7.0
Magick.NET-Q16-OpenMP-x64
< 14.7.0
14.7.0
Magick.NET-Q16-arm64
< 14.7.0
14.7.0
Magick.NET-Q16-x64
< 14.7.0
14.7.0
Magick.NET-Q16-x86
< 14.7.0
14.7.0
Magick.NET-Q8-AnyCPU
< 14.7.0
14.7.0
Magick.NET-Q8-OpenMP-arm64
< 14.7.0
14.7.0
Magick.NET-Q8-OpenMP-x64
< 14.7.0
14.7.0
Magick.NET-Q8-arm64
< 14.7.0
14.7.0
Magick.NET-Q8-x64
< 14.7.0
14.7.0
Magick.NET-Q8-x86
< 14.7.0
14.7.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

Magick.NET-Q16-AnyCPU NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q16-AnyCPU --version 14.7.0

Magick.NET-Q16-HDRI-AnyCPU NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q16-HDRI-AnyCPU --version 14.7.0

Magick.NET-Q16-HDRI-OpenMP-arm64 NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q16-HDRI-OpenMP-arm64 --version 14.7.0

Magick.NET-Q16-HDRI-OpenMP-x64 NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q16-HDRI-OpenMP-x64 --version 14.7.0

Magick.NET-Q16-HDRI-arm64 NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q16-HDRI-arm64 --version 14.7.0

Magick.NET-Q16-HDRI-x64 NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q16-HDRI-x64 --version 14.7.0

Magick.NET-Q16-HDRI-x86 NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q16-HDRI-x86 --version 14.7.0

Magick.NET-Q16-OpenMP-arm64 NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q16-OpenMP-arm64 --version 14.7.0

Magick.NET-Q16-OpenMP-x64 NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q16-OpenMP-x64 --version 14.7.0

Magick.NET-Q16-arm64 NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q16-arm64 --version 14.7.0

Magick.NET-Q16-x64 NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q16-x64 --version 14.7.0

Magick.NET-Q16-x86 NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q16-x86 --version 14.7.0

Magick.NET-Q8-AnyCPU NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q8-AnyCPU --version 14.7.0

Magick.NET-Q8-OpenMP-arm64 NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q8-OpenMP-arm64 --version 14.7.0

Magick.NET-Q8-OpenMP-x64 NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q8-OpenMP-x64 --version 14.7.0

Magick.NET-Q8-arm64 NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q8-arm64 --version 14.7.0

Magick.NET-Q8-x64 NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q8-x64 --version 14.7.0

Magick.NET-Q8-x86 NuGet → 14.7.0

dotnet
dotnet add package Magick.NET-Q8-x86 --version 14.7.0

Severity breakdown

CVSS 3.1 3.7

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

Weakness

CWE-125: Out-of-bounds Read

The product reads data past the end, or before the beginning, of the intended buffer.

How to prevent it
  • Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright. To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.
  • Architecture and Design: Use a language that provides appropriate memory abstractions.

CWE-401: Missing Release of Memory after Effective Lifetime

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

How to prevent it
  • Implementation: Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone. For example, glibc in Linux provides protection against free of invalid pointers. When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391]. To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.
  • Architecture and Design: Use an abstraction library to abstract away risky APIs. Not a complete solution.
  • Architecture and Design, Build and Compilation: Consider using the Boehm-Demers-Weiser garbage collector (bdwgc), which can help avoid leaks.

CWE-404: Improper Resource Shutdown or Release

The product does not release or incorrectly releases a resource before it is made available for re-use.

How to prevent it
  • Requirements: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.
  • Implementation: It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free memory in a function. If you allocate memory that you intend to free upon completion of the function, you must be sure to free the memory at all exit points for that function including error conditions.
  • Implementation: Memory should be allocated/freed using matching functions such as malloc/free, new/delete, and new[]/delete[].
  • Implementation: When releasing a complex object or structure, ensure that you properly dispose of all of its member components, not just the object itself.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-j7hp-h8jx-5ppr
libwebp: OOB write in BuildHuffmanTable
High Known exploited Also affects magick.net-q16-anycpu
GHSA-cvhv-g4rq-3hmw
ImageMagick: Memory Leak when providing invalid options to the cli
Medium Also affects Magick.NET-Q16-AnyCPU
GHSA-h22j-f9xw-xjjm
ImageMagick: Integer Overflow in JNX decoder causes heap buffer over-write when processing extremly large files on 32-bit builds
Medium Also affects Magick.NET-Q16-AnyCPU
GHSA-422r-8c97-xcg4
ImageMagick: Heap Buffer Over-Write in fx operation
Medium Also affects Magick.NET-Q16-AnyCPU
GHSA-f5m7-cqgw-8hm7
ImageMagick: Heap Buffer Over-Write in morphology operation when an invalid kernel is provided
Medium Also affects Magick.NET-Q16-AnyCPU
GHSA-hc76-7mpc-qjqh
ImageMagick: Code injection in HTML encoder due to incomplete fix of CVE-2026-25797
Medium Also affects Magick.NET-Q16-AnyCPU
GHSA-56m6-8q75-f2rw
ImageMagick: Policy Bypass due to an incomplete fix of CVE-2026-49219
Medium Also affects Magick.NET-Q16-AnyCPU
GHSA-h5r4-w88w-7ccr
ImageMagick: Memory Leak in TIFF encoder when invalid tiff:tile-geometry is specified
Low Also affects Magick.NET-Q16-AnyCPU
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor