Skip to content
Fencer Vulns
low 3.3

CVE-2020-27755 json

in SetImageExtent() of /MagickCore/image.c, an incorrect image depth size can cause a memory leak because the code which checks for the pro…

published 2020-12-08 5 y ago modified 2026-07-30 3 mo ago also EUVD-2020-20259 , JLSEC-2026-853

cvss
3.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

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.

Patch / fix

  • julia ImageMagick_jll 6.9.12+0
  • imagemagick imagemagick 6.9.10-69, 7.0.9-0
  • imagemagick Debian 14, Debian 13, Debian 12 8:6.9.11.24+dfsg-1

debian advisories DEBIAN-CVE-2020-27755

  • imagemagick Ubuntu 18.04 LTS 8:6.9.7.4+dfsg-16ubuntu6.11
  • imagemagick Ubuntu 20.04 LTS 8:6.9.10.23+dfsg-2.1ubuntu11.4
  • imagemagick Ubuntu Pro 16.04 LTS 8:6.8.9.9-7ubuntu5.16+esm11

ubuntu advisories UBUNTU-CVE-2020-27755

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • ImageMagick SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES for SAP 12 SP3 +16 more 6.8.8.1-71.154.1
  • ImageMagick SLES for SAP 15 SP1, SLES for SAP 15, SLES 15-LTSS +12 more 7.0.7.34-3.90.1
  • ImageMagick SLE Module for Development Tools 15 SP2, SLE Module for Desktop Applications 15 SP2 7.0.7.34-10.9.1
  • ImageMagick SLES 11 SP4-LTSS, SLE Point of Sale 11 SP3 6.4.3.6-78.135.1

suse advisories SUSE-SU-2021:0199-1SUSE-SU-2021:0156-1SUSE-SU-2021:0153-1SUSE-SU-2021:14598-1

  • ImageMagick openSUSE Tumbleweed 7.1.0.9-1.1
  • ImageMagick openSUSE Leap 15.1 7.0.7.34-lp151.7.26.1
  • ImageMagick openSUSE Leap 15.2 7.0.7.34-lp152.12.9.1

opensuse advisories openSUSE-SU-2024:11564-1openSUSE-SU-2021:0148-1openSUSE-SU-2021:0136-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-27755 updated cvss 3.3

ImageMagick: memory leaks in ResizeMagickMemory function in ImageMagick/MagickCore/memory.c

  • Red Hat Enterprise Linux 5 ImageMagick Red Hat Enterprise Linux 6 ImageMagick, ImageMagick-c++, ImageMagick-perl Red Hat Enterprise Linux 7 ImageMagick, ImageMagick-c++, ImageMagick-perl
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 9 ImageMagick
    affected: no fix available
  • Red Hat Enterprise Linux 8 inkscape, inkscape-view
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.86% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=1894232 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P
OSV 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
julia ImageMagick_jll
<6.9.12+0
6.9.12+0

Affected products

  • n/a ImageMagick

Classification

Weakness
  • CWE-401 Missing Release of Memory after Effective Lifetime

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.