Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
94 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
An incorrect check in the JP2 will result in an heap buffer over-write of a single byte when specifying certain options.
Recommended action: Upgrade to 14.13.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Due to a missing depth check a stack overflow can occur in the fx operation by passing a crafted argument.
Recommended action: Upgrade to 14.13.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A crafted MSL image can trigger a heap-use-after-free.
Recommended action: Upgrade to 14.13.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Due to a missing check in the MIFF decoder a crafted file could cause an infinite loop resulting in CPU exhaustion.
Recommended action: Upgrade to 14.13.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When using LZMA compression in the MIFF encoder an out of bounds write can occur due to a missing check.
Recommended action: Upgrade to 14.13.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When reading multiple images with different dimensions an out of bounds heap write can occur.
Recommended action: Upgrade to 14.13.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Because of a missing check in the MNG coder it would be possible to read more images than the list limit policy would allow resulting in excessive resource use.
Recommended action: Upgrade to 14.13.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When performing a polynomial distortion an out of bounds over-read of 24 bytes can occur when specifying specific arguments.
Recommended action: Upgrade to 14.13.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Due to a missing check in the PSD decoder it would be possible to bypass the list-length resource policy when decoding a PSD image. Other security limits would still apply.
Recommended action: Upgrade to 14.13.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
An of by one in the meta encoder could result in an out of bounds read of a single byte in the meta encoder.
Recommended action: Upgrade to 14.13.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
An invalid connected-components:keep-top value could result in a heap buffer over-read when performing the connected components operation.
Recommended action: Upgrade to 14.13.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When writing an IPTC output file a malicious input file could cause an out of bounds read of a single byte.
Recommended action: Upgrade to 14.13.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When the PNG encoder fails to write an MNG image it can leak memory.
Recommended action: Upgrade to 14.12.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When the connected-components: define specifies an invalid index and out of bound operation will result in an access violation.
Recommended action: Upgrade to 14.12.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
An unrecognized magnify:method will result in an out of bounds read in the magnify operation.
Recommended action: Upgrade to 14.12.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The patch for GHSA-7h7q-j33q-hvpf was incomplete and still allows a stack buffer overflow for the multi frame images.
Recommended action: Upgrade to 14.12.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
An incorrect morphology would allow an out of bounds read of a single pixel.
Recommended action: Upgrade to 14.12.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The FTXT encoder lacks a boundary check when parsing ftxt:format, resulting in an out of bounds read.
Recommended action: Upgrade to 14.12.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The NewXMLTree method contains a bug that could result in a crash due to an out of write bounds of a single zero byte.
Recommended action: Upgrade to 14.11.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Specially crafted SVG file make segmentation fault and generate trash files in "/tmp", possible to leverage DoS. Operating system, version and so on Linux, Debian (Buster) LTS core 5.10 / Parrot OS 5.1 (Electro Ara) Tested ImageMagick version 6.9.11-60, 7.1.0-62 Details A specially created SVG file that loads by itself and make segmentation fault. Remote attackers can take advantage of this vulnerability to cause a denial of service of the generated SVG file. It seems that this error affects a lot of websites and causes a generating trash files in when uploading this PC file to the server. I think it's better to check the file descriptor coming from itself before executing . PoC 1. Generate SVG file: 2. Run some commands for verification: Impact Possible DOS, because when ImageMagick crashes it generates a lot of trash files. This trash file can be large, if SVG file contains many render action. Additional impact In DOS attack if remount attacker uploads an SVG file of size…
Recommended action: Upgrade to 13.0.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A 32-bit unsigned integer overflow in the XWD (X Windows) encoder can cause an undersized heap buffer allocation. When writing a extremely large image an out of bounds heap write can occur.
Recommended action: Upgrade to 14.10.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A crafted image could cause an out of bounds heap write inside the WaveletDenoiseImage method. When processing a crafted image with the -wavelet-denoise operation an out of bounds write can occur.
Recommended action: Upgrade to 14.10.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
BilateralBlurImage contains a heap buffer over-read caused by an incorrect conversion. When processing a crafted image with the -bilateral-blur operation an out of bounds read can occur.
Recommended action: Upgrade to 14.10.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A heap-based buffer overflow in the UHDR encoder can happen due to truncation of a value and it would allow an out of bounds write.
Recommended action: Upgrade to 14.10.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
MagnifyImage uses a fixed-size stack buffer. When using a specific image it is possible to overflow this buffer and corrupt the stack.
Recommended action: Upgrade to 14.10.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.