Resource exhaustion in Libjpeg-Turbo
CVE-2019-13960
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 · last modified .
CVSS v3 metric
CVSS v3 base score 5.5 (Medium). Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS 0.010, 61.8th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Libjpeg-Turbo — versions 2.0.2
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (ARPSyndicate/cvemon, s-cube-xmu/Bug_List). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/libjpeg-turbo/libjpeg-turbo/issues/337 (Exploit, Third Party Advisory)
- libjpeg-turbo.org/pmwiki/uploads/About/TwoIssueswiththeJPEGStandard.pdf (Exploit, Patch, Vendor Advisory)