LiveActive security incident?Get immediate response
CVE Record

CVE-2019-13960: In libjpeg-turbo 2.0.2, a large amount of memory can be used during processing of an invalid progressive JP...

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes a denial-of-service risk in libjpeg-turbo 2.0.2. A malformed progressive JPEG with misleading width and height values can drive unusually high memory use during processing. The main business concern is service instability where systems accept or process untrusted images without strict limits.

Executive priority

Prioritize review for public upload, media conversion, document-processing, or customer-support systems. Without exposed image ingestion, urgency is lower. Because severity and affected-product metadata are incomplete, validate dependency usage before assigning broad remediation work.

Technical view

libjpeg-turbo 2.0.2 may consume a large amount of memory while decompressing an invalid progressive JPEG containing incorrect header dimensions. The CVE notes the vendor expects applications to treat libjpeg warnings as fatal and/or enforce resource and image-size limits for denial-of-service-sensitive use cases.

Likely exposure

Exposure is most likely in applications or services using libjpeg-turbo 2.0.2 to process progressive JPEGs from untrusted or semi-trusted sources. The provided affected-product metadata is incomplete, so downstream package impact must be verified locally.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The described impact is resource exhaustion, not code execution. Risk depends heavily on whether image processing continues after warnings and whether memory or image-size limits exist.

Researcher notes

The CVE record frames this as memory overuse from invalid progressive JPEG dimensions. It also records a vendor expectation that applications handle warnings and limits defensively. No CVSS, CWE, patch version, or complete affected-product data is provided in the bundle.

Mitigation direction

  • Check vendor guidance and downstream package advisories for fixed or recommended versions.
  • Configure applications to treat libjpeg warnings as fatal during decompression.
  • Enforce maximum image dimensions before image processing begins.
  • Apply memory and CPU limits around image upload or conversion workers.
  • Restrict untrusted image processing where operational impact would be severe.

Validation and detection

  • Inventory services and dependencies using libjpeg-turbo 2.0.2.
  • Identify workflows that process user-supplied progressive JPEG files.
  • Confirm decompression stops when libjpeg warnings occur.
  • Verify image dimension and resource limits are enforced.
  • Review monitoring for image-processing memory spikes or worker restarts.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-13960 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.