Skip to content
Fencer Intel
low 3.3

CVE-2020-27754 json

In IntensityCompare() of /magick/quantize.c, there are calls to PixelPacketIntensity() which could return overflowed values to the caller w…

published 5y ago modified 3mo ago also EUVD-2020-20258 , JLSEC-2026-852

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

Summary

In IntensityCompare() of /magick/quantize.c, there are calls to PixelPacketIntensity() which could return overflowed values to the caller when ImageMagick processes a crafted input file. To mitigate this, the patch introduces and uses the ConstrainPixelIntensity() function, which forces the pixel intensities to be within the proper bounds in the event of an overflow. This flaw affects ImageMagick versions prior to 6.9.10-69 and 7.0.8-69.

Patch / fix

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

debian advisories DEBIAN-CVE-2020-27754

  • 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-27754

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 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-2021:0148-1openSUSE-SU-2021:0136-1

Is CVE-2020-27754 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-27754 updated cvss 3.3

ImageMagick: outside the range of representable values of type 'long' and signed integer overflow at MagickCore/quantize.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

1.14% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=1894231 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-190 Integer Overflow or Wraparound

References

Sources

Fencer Intel 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.