CVE-2017-15601: Buffer Overflow
First published: Wed Oct 18 2017(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| libextractor | =1.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-15601?
CVE-2017-15601 has been classified as a high severity vulnerability due to the potential for remote code execution caused by the heap-based buffer overflow.
How do I fix CVE-2017-15601?
To fix CVE-2017-15601, upgrade to GNU Libextractor version 1.6 or apply a suitable patch to the vulnerable version.
What impact does CVE-2017-15601 have on systems running GNU Libextractor 1.4?
CVE-2017-15601 can lead to denial of service or remote code execution on systems using GNU Libextractor 1.4, potentially compromising the integrity of the affected system.
Is CVE-2017-15601 exploitable in a network setting?
Yes, CVE-2017-15601 can be exploited in a network setting if an attacker can deliver specially crafted PNG files to the vulnerable application.
What components of GNU Libextractor are affected by CVE-2017-15601?
The vulnerability in CVE-2017-15601 specifically affects the EXTRACTOR_png_extract_method function found in the plugins/png_extractor.c file.
- agent/weakness
- agent/tags
- agent/event
- agent/references
- agent/severity
- agent/author
- agent/type
- agent/description
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gnu
- canonical/libextractor
- version/libextractor/1.4