CVE-2015-8126
What it is
Multiple buffer overflows in the (1) png_set_PLTE and (2) png_get_PLTE functions in libpng before 1.0.64, 1.1.x and 1.2.x before 1.2.54, 1.3.x and 1.4.x before 1.4.17, 1.5.x before 1.5.24, and 1.6.x before 1.6.19 allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a small bit-depth value in an IHDR (aka image header) chunk in a PNG image.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 10.3% chance of exploitation in the next 30 days (EPSS). Higher than most.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 10.3% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 10.3% · EPSS, next 30 days
- Weakness
- CWE-120 · Classic buffer overflow
- Record status
- Modified
Affected
- Libpng < 1.0.64
- Libpng < 1.2.54
- Libpng < 1.4.17
- Libpng < 1.5.24
- Libpng < 1.6.19
- Fedoraproject Fedora 21
- Fedoraproject Fedora 22
- Fedoraproject Fedora 23
Attack profile CVSS 2.0 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
Raw vector
AV:N/AC:L/Au:N/C:P/I:P/A:P
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2015-8126.md and follow it. Check whether this project is affected by CVE-2015-8126. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://code.google.com/p/chromium/issues/detail?id=560291
- https://code.google.com/p/chromium/issues/detail?id=560291
References
- http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html
- http://lists.apple.com/archives/security-announce/2016/Mar/msg00004.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-November/172324.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-November/172620.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-November/172647.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-November/172663.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-November/172769.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-November/172797.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-November/172823.html
- http://lists.fedoraproject.org/pipermail/package-announce/2016-February/177344.html
- http://lists.fedoraproject.org/pipermail/package-announce/2016-February/177382.html
- http://lists.fedoraproject.org/pipermail/package-announce/2016-January/174905.html
- http://lists.fedoraproject.org/pipermail/package-announce/2016-January/174936.html
- http://lists.fedoraproject.org/pipermail/package-announce/2016-January/175073.html
- http://lists.opensuse.org/opensuse-security-announce/2015-11/msg00033.html
- http://lists.opensuse.org/opensuse-security-announce/2015-11/msg00034.html
- http://lists.opensuse.org/opensuse-security-announce/2016-01/msg00038.html
- http://lists.opensuse.org/opensuse-security-announce/2016-01/msg00041.html
- http://lists.opensuse.org/opensuse-security-announce/2016-01/msg00042.html
- http://lists.opensuse.org/opensuse-security-announce/2016-01/msg00043.html
- http://lists.opensuse.org/opensuse-security-announce/2016-01/msg00044.html
- http://lists.opensuse.org/opensuse-security-announce/2016-01/msg00045.html
- http://lists.opensuse.org/opensuse-security-announce/2016-01/msg00047.html
- http://lists.opensuse.org/opensuse-security-announce/2016-01/msg00048.html
- http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00014.html