- 60comments
- 80comments
- 52comments
- 32comments
- 38comments
- 86comments
- 21comments
- 397comments
- 457comments
- 24comments
- 13comments
- 162comments
- 115comments
- 16comments
- 19comments
- 23comments
- 126comments
- 127comments
- 258comments
- 26comments
- 31comments
- 21comments
- 75comments
- 434comments
- 197comments
- 734comments
- 47comments
- 171comments
- 444comments
- 36comments
Affects back to version 1.6.0 released Feb 14, 2013
rust rewrite when?
Chrome is already in the process of removing libpng.
For those curious on what to instead, it seems like they made an in house Skia module (using Rust) named SkPngRustDecoder (and Encoder).
…which appears to wrap the png crate. (Good, so not a rewrite)
https://www.cve.org/CVERecord/SearchResults?query=rust
It’s fantastic they were able to find these issues!
That four new CVEs (two high-severity!) were found in a mature and well-tested library like png reminds me how non-trivial and unforgiving software engineering can be.
Security flaws are often just waiting behind the corner: this should be humbling lesson for all of us.
What world is the author living in where PNGs aren't very frequently read and written with no user interaction. The web obviously displays PNGs with no prompt, sites can generate PNGs with canvas trivially and with no explicit permission. PNGs are also often displayed in notifications and may come from untrustworthy sources.
This feels like an irresponsible downplay of the severity.
I thought this initially too, but there's a comment on https://bugzilla.mozilla.org/show_bug.cgi?id=2001758#c5 that suggests a belief it doesn't affect Firefox at all. So I don't know if the surface for these is particularly obscure such that browsers are insulated?