libjpeg-turbo 2.0.2
Approved changes feed: RSS · Atom
cpe:2.3:a:libjpeg-turbo:libjpeg-turbo:2.0.2:*:*:*:*:*:*:*part: a version: 2.0.2 update: *
| Vendor | Libjpeg Turbo (7cd72dca-911c-5c6a-bfe0-e21a12392cba) |
|---|---|
| Product | Libjpeg Turbo (939e3cc2-e95f-58d4-865b-32b16b9cc62f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from NVD CPE 2.0 feed
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:deb/debian/libjpeg-turbo |
purl2cpe | 2026-06-01 10:14:03.043931 |
pkg:deb/ubuntu/libjpeg-turbo |
purl2cpe | 2026-06-01 10:14:03.043932 |
pkg:github/libjpeg-turbo/libjpeg-turbo |
purl2cpe | 2026-06-01 10:14:03.043933 |
pkg:gitlab/redhat/libjpeg-turbo |
purl2cpe | 2026-06-01 10:14:03.043935 |
pkg:rpm/centos/libjpeg-turbo |
purl2cpe | 2026-06-01 10:14:03.043936 |
pkg:rpm/fedora/libjpeg-turbo |
purl2cpe | 2026-06-01 10:14:03.043938 |
pkg:rpm/opensuse/libjpeg-turbo |
purl2cpe | 2026-06-01 10:14:03.043939 |
pkg:sourceforge/libjpeg-turbo |
purl2cpe | 2026-06-01 10:14:03.043940 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-13960 |
vulnerable | 2026-06-08 05:12:52.880587 |
Details available
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-18T18:52:29.000Z
Updated: 2024-08-05T00:05:44.065Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.