CVE-2015-8126: Multiple buffer overflows in libpng
web.nvd.nist.gov
CVE-2015-8126: Multiple buffer overflows in libpng
1–10 of 88 posts
Re: CVE-2015-8126: Multiple buffer overflows in libpng
#2Re: CVE-2015-8126: Multiple buffer overflows in libpng
#3Patching this properly will require not just replacing a centralized copy of libpng, but scanning all binaries for statically-linked copies. There might be some tools left over from the last time libpng got into trouble; this would be a very good time to update and link to them. Some categories of software that are at particularly high risk right now:
* Web browsers. Sandboxing likely helps, but there's a possibility that there are some usages (eg favicons) that decode outside the sandbox.
* MMS on Android (possibly remote root on phones with no user interaction)
* Any server that accepts PNG uploads and processes them (eg, user avatar thumbnail generation)
* Anything which shows people user-provided avatar images (eg, IM clients)
* Video games which download levels that can contain images
* File browsers which show image previews
* Music players which display album covers
Expect malicious images to start appearing everywhere, and soon. If you're responsible for the computer security anywhere, this is a drop-everything priority.
Re: CVE-2015-8126: Multiple buffer overflows in libpng
#4Re: CVE-2015-8126: Multiple buffer overflows in libpng
#5Uh oh. It's time for the monthly global computer security meltdown. Again, but worse this time. Security vulnerabilities in libpng are a huge deal; they affect lots and lots of different programs, including things people don't usually think of, and many them embed their own copies of libpng which makes them hard to update. The last time there was a security vulnerability in libpng, it took years before it was fixed e…
Re: CVE-2015-8126: Multiple buffer overflows in libpng
#6What are the practical implications of this?
Re: CVE-2015-8126: Multiple buffer overflows in libpng
#7Uh oh. It's time for the monthly global computer security meltdown. Again, but worse this time. Security vulnerabilities in libpng are a huge deal; they affect lots and lots of different programs, including things people don't usually think of, and many them embed their own copies of libpng which makes them hard to update. The last time there was a security vulnerability in libpng, it took years before it was fixed e…
Is this more than a denial of service due to crashes?
Crashes are better than privilege escalation, but they do not mean that privilege escalation is impossible.
Re: CVE-2015-8126: Multiple buffer overflows in libpng
#8Uh oh. It's time for the monthly global computer security meltdown. Again, but worse this time. Security vulnerabilities in libpng are a huge deal; they affect lots and lots of different programs, including things people don't usually think of, and many them embed their own copies of libpng which makes them hard to update. The last time there was a security vulnerability in libpng, it took years before it was fixed e…
Is this more than a denial of service due to crashes?
> allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact
As far as I understand, trying to predict what is possible by exploiting a buffer overflow is hard because it depends on many specifics, such as compiler options used, OS protections, ...
Re: CVE-2015-8126: Multiple buffer overflows in libpng
#9Uh oh. It's time for the monthly global computer security meltdown. Again, but worse this time. Security vulnerabilities in libpng are a huge deal; they affect lots and lots of different programs, including things people don't usually think of, and many them embed their own copies of libpng which makes them hard to update. The last time there was a security vulnerability in libpng, it took years before it was fixed e…
Is this more than a denial of service due to crashes?
Re: CVE-2015-8126: Multiple buffer overflows in libpng
#10>and 1.6.x before 1.6.19
Unfortunately, the latest version on libpng site [0] is 1.6.18.
Why was this CVE announced before the patch and version update was released?