Skip to content
Fencer Intel
high 7.1

CVE-2020-6624 json

jhead through 3.04 has a heap-based buffer over-read in process_DQT in jpgqguess.c.

published 6y ago modified 4mo ago also EUVD-2020-27772

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

Summary

jhead through 3.04 has a heap-based buffer over-read in process_DQT in jpgqguess.c.

Patch / fix

  • jhead Ubuntu 18.04 LTS 1:3.00-8~ubuntu0.1
  • jhead Ubuntu 20.04 LTS 1:3.04-1ubuntu0.1
  • jhead Ubuntu Pro 14.04 LTS 1:2.97-1+deb8u2ubuntu0.1~esm1
  • jhead Ubuntu Pro 16.04 LTS 1:3.00-4+deb9u1ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2020-6624

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

  • jhead Package Hub 15 SP2 3.06.0.1-bp152.4.6.1
  • jhead openSUSE Leap 15.2 3.06.0.1-lp152.7.6.1

opensuse advisories openSUSE-SU-2021:0752-1openSUSE-SU-2021:0743-1

Is CVE-2020-6624 in your stack? 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-6624 updated cvss 6.6

jhead: heap-based buffer overflow in process_DQT in jpgqguess.c

  • Red Hat All currently supported Red Hat products
    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.43% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugs.launchpad.net https://bugs.launchpad.net/ubuntu/+source/jhead/+bug/1858744 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 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.