CVE-2020-6624

Exp

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

Published: 2020-01-09 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2020-6624 is rated High Exploit Risk (68.1/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.70%). Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2020-6624

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2020-6624

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-30 1.01% 0.70% -0.31%
2 2025-12-08 1.15% 1.01% -0.14%
3 2025-11-21 1.15%

Full EPSS history (17 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-6624

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.1 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 5.2 [email protected]
5.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
8.6 4.9 [email protected]

Weakness enumeration for CVE-2020-6624

OS Trackers for CVE-2020-6624

vendor priority summary link
debian unimportant CVE-2020-6624 unimportant priority: Debian including 1 source packages (jhead), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2020-6624
gentoo normal CVE-2020-6624: 1 GLSA(s) (202406-05), 1 atom(s) (media-gfx/jhead); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2020-6624
ubuntu medium CVE-2020-6624 medium priority: Ubuntu including 1 source packages (jhead), 13 status rows across 13 suites (bionic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, trusty, upstream, xenial): ignored 5, released 5, not-affected 3. https://ubuntu.com/security/CVE-2020-6624

Affected software / configurations for CVE-2020-6624

Vendor Product Version Raw CPE
jhead_project jhead <= 3.04 cpe:2.3:a:jhead_project:jhead:*:*:*:*:*:*:*:*

References for CVE-2020-6624

URL Tags
https://bugs.gentoo.org/711220#c3 Issue Tracking Third Party Advisory
https://bugs.gentoo.org/876247#c0 Issue Tracking Third Party Advisory
https://bugs.launchpad.net/ubuntu/+source/jhead/+bug/1858744 Exploit Issue Tracking Third Party Advisory
https://security.gentoo.org/glsa/202007-17 Third Party Advisory
cvelogic Threat Intelligence