Libextractor vulnerabilitiesRanked by how likely they are to be used.
Libextractor is made by Gnu. We track 13 published vulnerabilities in it, across 20 versions. None of them is on the list of flaws known to be exploited today. If you run Libextractor, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Libextractor vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Libextractor's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Libextractor 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.
- 2.6%CVE-2018-16430High
GNU Libextractor through 1.7 has an out-of-bounds read vulnerability in EXTRACTOR_zip_extract_method() in zip_extractor.c.
- 2.6%CVE-2017-15267High
In GNU Libextractor 1.4, there is a NULL Pointer Dereference in flac_metadata in flac_extractor.c.
- 2.4%CVE-2017-17440Medium
GNU Libextractor 1.6 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted GIF, IT (Impulse Tracker), NSFE, S3M (Scream Tracker 3), SID, or XM (eXtended...
- 2.2%CVE-2018-20430Medium
GNU Libextractor through 1.8 has an out-of-bounds read vulnerability in the function history_extract() in plugins/ole2_extractor.c, related to EXTRACTOR_common_convert_to_utf8 in common/convert.c.
- 2.2%CVE-2018-20431Medium
GNU Libextractor through 1.8 has a NULL Pointer Dereference vulnerability in the function process_metadata() in plugins/ole2_extractor.c.
- 2.1%CVE-2017-15600High
In GNU Libextractor 1.4, there is a NULL Pointer Dereference in the EXTRACTOR_nsf_extract_method function of plugins/nsf_extractor.c.
- 2.1%CVE-2018-14346High
GNU Libextractor before 1.7 has a stack-based buffer overflow in ec_read_file_func (unzip.c).
- 1.7%CVE-2018-14347Medium
GNU Libextractor before 1.7 contains an infinite loop vulnerability in EXTRACTOR_mpeg_extract_method (mpeg_extractor.c).
- 1.7%CVE-2019-15531Medium
GNU Libextractor through 1.9 has a heap-based buffer over-read in the function EXTRACTOR_dvi_extract_method in plugins/dvi_extractor.c.
- 1.6%CVE-2017-15601High
In GNU Libextractor 1.4, there is a heap-based buffer overflow in the EXTRACTOR_png_extract_method function in plugins/png_extractor.c, related to processiTXt and stndup.
Running Libextractor? 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
GNU Libextractor through 1.7 has an out-of-bounds read vulnerability in EXTRACTOR_zip_extract_method() in zip_extractor.c.
- Matched to
- Libextractor 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.
We track 13 published vulnerabilities listed under the name Libextractor, across 20 versions.
None of Libextractor's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Libextractor. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.