CVE-2019-13960

Exp

In libjpeg-turbo 2.0.2, a large amount of memory can be used during processing of an invalid progressive JPEG image containing incorrect width and height values in the image header. NOTE: the vendor's expectation, for use cases in which this memory usage would be a denial of service, is that the application should interpret libjpeg warnings as fatal errors (aborting decompression) and/or set limits on resource consumption or image sizes

Published: 2019-07-18 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-13960 is rated Exploit Available (55.2/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.29%). 2 public exploit reference(s) are indexed (Exploit-DB). 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-2019-13960

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

Exploit prediction scoring system (EPSS) score for CVE-2019-13960

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 2025-11-21 0.16% 0.29% +0.12%
2 2025-11-18 0.29% 0.16% -0.12%
3 2025-08-30 — 0.29% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-13960

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.0 MEDIUM
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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:N)
Doesn’t really leak secrets in a meaningful 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 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/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:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2019-13960

OS Trackers for CVE-2019-13960

vendor priority summary link
alpine — CVE-2019-13960: 1 source package rows (libjpeg-turbo); 5 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 0, open 5. https://security.alpinelinux.org/vuln/CVE-2019-13960
redhat low — https://access.redhat.com/security/cve/CVE-2019-13960
ubuntu negligible CVE-2019-13960 negligible priority: Ubuntu including 1 source packages (libjpeg-turbo), 7 status rows across 7 suites (bionic, disco, eoan, focal, trusty, upstream, xenial): not-affected 5, ignored 1, needs-triage 1. https://ubuntu.com/security/CVE-2019-13960

Affected software / configurations for CVE-2019-13960

Vendor Product Version Raw CPE
libjpeg-turbo libjpeg-turbo 2.0.2 cpe:2.3:a:libjpeg-turbo:libjpeg-turbo:2.0.2:*:*:*:*:*:*:*

References for CVE-2019-13960

cvelogic Threat Intelligence