ImageMagick before 7.1.2-15 and 6.9.13-40 contains a memory leak in coders/txt.c when processing TXT files with texture attributes: the texture object allocated via ReadImage is not released when GetTypeMetrics fails, leaking memory each time a crafted TXT file with a texture attribute is processed.
Weakness
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Imagemagick | Imagemagick | * | 6.9.13-40 (excluding) |
| Imagemagick | Imagemagick | 7.0.0-0 (including) | 7.1.2-15 (excluding) |
| Imagemagick | Ubuntu | esm-apps/focal | * |
| Imagemagick | Ubuntu | esm-apps/jammy | * |
| Imagemagick | Ubuntu | esm-apps/noble | * |
| Imagemagick | Ubuntu | esm-infra-legacy/trusty | * |
| Imagemagick | Ubuntu | esm-infra-legacy/xenial | * |
| Imagemagick | Ubuntu | esm-infra/bionic | * |
| Imagemagick | Ubuntu | jammy | * |
| Imagemagick | Ubuntu | noble | * |
| Imagemagick | Ubuntu | questing | * |
| Imagemagick | Ubuntu | upstream | * |
Potential Mitigations
- 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.