Libjpeg-Turbo vulnerabilitiesNone on the known-exploited list.
Libjpeg-Turbo has 16 published vulnerabilities across 1 product in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Libjpeg-Turbo, with 16. If you run Libjpeg-Turbo software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Libjpeg-Turbo products have the most vulnerabilities?
Libjpeg-Turbo leads with 16 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Libjpeg-Turbo vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Libjpeg-Turbo's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Libjpeg-Turbo flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 9.7%CVE-2013-6629Medium
The get_sos function in jdmarker.c in (1) libjpeg 6b and (2) libjpeg-turbo through 1.3.0, as used in Google Chrome before 31.0.1650.48, Ghostscript, and other products, does not check for certain duplications of...
- 4.4%CVE-2016-3616High
The cjpeg utility in libjpeg allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) or execute arbitrary code via a crafted file.
- 3.4%CVE-2018-1152Medium
libjpeg-turbo 1.5.90 is vulnerable to a denial of service vulnerability caused by a divide by zero when processing a crafted BMP image.
- 3.2%CVE-2014-9092Medium
libjpeg-turbo before 1.3.1 allows remote attackers to cause a denial of service (crash) via a crafted JPEG file, related to the Exif marker.
- 3.2%CVE-2020-13790High
libjpeg-turbo 2.0.4, and mozjpeg 4.0.0, has a heap-based buffer over-read in get_rgb_row() in rdppm.c via a malformed PPM input file.
- 3.1%CVE-2018-14498Medium
get_8bit_row in rdbmp.c in libjpeg-turbo through 1.5.90 and MozJPEG through 3.3.1 allows attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted 8-bit BMP in which one...
- 2.7%CVE-2020-17541High
Libjpeg-turbo all version have a stack-based buffer overflow in the "transform" component.
- 2.4%CVE-2017-15232Medium
libjpeg-turbo 1.5.2 has a NULL Pointer Dereference in jdpostct.c and jquant1.c via a crafted JPEG file.
- 2.0%CVE-2018-20330High
The tjLoadImage function in libjpeg-turbo 2.0.1 has an integer overflow with a resultant heap-based buffer overflow via a BMP image because multiplication of pitch and height is mishandled, as demonstrated by tjbench.
- 1.7%CVE-2018-19664Medium
libjpeg-turbo 2.0.1 has a heap-based buffer over-read in the put_pixel_rows function in wrbmp.c, as demonstrated by djpeg.
All Libjpeg-Turbo products we track.
1 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Libjpeg-Turbo? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
The get_sos function in jdmarker.c in (1) libjpeg 6b and (2) libjpeg-turbo through 1.3.0, as used in Google Chrome before 31.0.1650.48, Ghostscript, and other products, does not check for certain duplications of component data during the reading of segments that follow Start Of Scan (SOS) JPEG markers, which allows remote attackers to obtain sensitive information from uninitialized memory locations via a crafted JPEG image.
- Matched to
- Libjpeg-Turbo on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 16 published vulnerabilities across 1 product and 50 versions from Libjpeg-Turbo.
None of Libjpeg-Turbo's vulnerabilities is on the list of flaws known to be exploited today.
Libjpeg-Turbo, with 16 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Libjpeg-Turbo products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.