Skip to content
Fencer Vulns
high 7.1

CVE-2020-14153 json

In IJG JPEG (aka libjpeg) from version 8 through 9c, jdhuff.c has an out-of-bounds array read for certain table pointers.

published 2020-06-15 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-6310

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

Summary

In IJG JPEG (aka libjpeg) from version 8 through 9c, jdhuff.c has an out-of-bounds array read for certain table pointers.

Patch / fix

  • libjpeg9 Ubuntu Pro 16.04 LTS 1:9b-1ubuntu1+esm1

ubuntu advisories UBUNTU-CVE-2020-14153

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

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-14153 updated cvss 7.1

libjpeg: out-of-bounds read for certain table pointers in jdhuff.c

  • Red Hat Enterprise Linux 5 libjpeg
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 6 libjpeg-turbo Red Hat Enterprise Linux 7 turbojpeg, libjpeg-turbo, libjpeg-turbo-utils Red Hat Enterprise Linux 8 turbojpeg, libjpeg-turbo, libjpeg-turbo-utils
    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.01% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/libjpeg-turbo/libjpeg-turbo/issues/445 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness

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.