CVE-2016-8699
Last modified
CVE-2016-8699 is a vulnerability of currently unknown severity. Heap-based buffer overflow in the bm_readbody_bmp function in bitmap_io.c in potrace before 1.13 allows remote attackers to have unspecified impact via a crafted BMP image, a different vulnerability than CVE-2016-8698, CVE-2016-8700, CVE-2016-8701, CVE-2016-8702, and CVE-2016-8703.. EPSS estimates a 1.98% chance of exploitation in the next 30 days.
Description
Heap-based buffer overflow in the bm_readbody_bmp function in bitmap_io.c in potrace before 1.13 allows remote attackers to have unspecified impact via a crafted BMP image, a different vulnerability than CVE-2016-8698, CVE-2016-8700, CVE-2016-8701, CVE-2016-8702, and CVE-2016-8703.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Potrace Project | Potrace | <= 1.12 |
References
- http://potrace.sourceforge.net/ChangeLogRelease Notes, Third Party Advisory
- http://www.openwall.com/lists/oss-security/2016/08/18/11Mailing List, Third Party Advisory
- http://www.openwall.com/lists/oss-security/2016/10/16/12Mailing List, Third Party Advisory
- http://www.securityfocus.com/bid/93778Third Party Advisory, VDB Entry
- http://potrace.sourceforge.net/ChangeLogRelease Notes, Third Party Advisory
- http://www.openwall.com/lists/oss-security/2016/08/18/11Mailing List, Third Party Advisory
- http://www.openwall.com/lists/oss-security/2016/10/16/12Mailing List, Third Party Advisory
- http://www.securityfocus.com/bid/93778Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-8699?
How severe is CVE-2016-8699?
How do I fix CVE-2016-8699?
Are you affected by CVE-2016-8699?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
