Patching the libwebp vulnerability across the Python ecosystem
sethmlarson.dev
sethmlarson.dev
Chrome: Heap buffer overflow in WebP (https://news.ycombinator.com/item?id=37478403) (333 points | 262 comments)
The WebP 0day (https://news.ycombinator.com/item?id=37600852) (440 points | 206 comments)
Google assigns a CVE for libwebp and gives it a 10.0 score (https://news.ycombinator.com/item?id=37657746) (261 points | 223 comments)
E.g. if I know pillow<5.0.1 (just making a version up) has this, it’s pretty trivial to find projects still using that. I know folks using e.g. pyproj that are entirely unaware of any need to update this.
However, that approach will only find vulnerable dependencies in Git repositories, not ones that exist in already-published binary artifacts.
With the work that the other maintainers have been doing recently to streamline the release process, it was pretty quick to do the packaging for the point release. (~ 50+ binary wheels, on combinations of pypy, cpython, musl, osx, windows, linux, x86 and arm across the supported python versions)