First published: Sat Jul 28 2012(Updated: )
Tom Lane (tgl) found an issue in ImageMagick. Basically <a href="https://access.redhat.com/security/cve/CVE-2011-3026">CVE-2011-3026</a> deals with libpng memory allocation, limitations have been added so that a bad PNG can't cause the system to allocate a lot of memory causing a denial of service. However on further investigation of ImageMagick Tom Lane found that PNG malloc function (Magick_png_malloc) in turn calls AcquireMagickMemory with an improper size argument: #ifdef PNG_USER_MEM_SUPPORTED static png_voidp Magick_png_malloc(png_structp png_ptr,png_uint_32 size) { (void) png_ptr; return((png_voidp) AcquireMagickMemory((size_t) size)); } This is incorrect, the size argument should be declared png_alloc_size_t according to 1.5, or png_size_t according to 1.2. "As this function stands, it invisibly does the wrong thing for any request over 4GB. On big-endian architectures it very possibly will do the wrong thing even for requests less than that. So the reason why the hard-wired 4GB limit prevents a core dump is that it masks the ABI mismatch here." So basically we have memory allocations problems that can probably lead to a denial of service.
Affected Software | Affected Version | How to fix |
---|---|---|
ImageMagick |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-844101 relates to a denial of service vulnerability due to improper memory allocation in ImageMagick.
REDHAT-BUG-844101 affects ImageMagick by allowing a malformed PNG file to potentially consume excessive memory resources.
To fix REDHAT-BUG-844101, you should update ImageMagick to the latest version that includes the patch addressing this vulnerability.
All versions of ImageMagick prior to the patch that addresses REDHAT-BUG-844101 are impacted.
While the recommended approach is to update ImageMagick, temporarily restricting input handling of PNG files can serve as a potential workaround.