4 ms·
Patching the libwebp vulnerability across the Python ecosystem
- deleted 3y ago[deleted]
- skilled 3y agoRelevant discussions on the CVE, Chrome: Heap buffer overflow in WebP (https://news.ycombinator.com/item?id=37478403 https://news.ycombinator.com/item?id=37478403) (333 points | 262 comments) The WebP 0day (https://news.ycombinator.com/item?id=37600852 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 https://news.ycombinator.com/item?id=37657746) (261 points | 223 comments)
- wiredfool 3y agoI'm a Pillow maintainer -- The Webp issue was sort of the best case for Pillow. It was high profile and embargoed so it was on our radar days before the patches dropped, and it was a drop-in fix for us, so no code changes required. 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)
- cozzyd 3y agoI'm glad my distro is vehemently against vendored libraries...
- appplication 3y agoInteresting. I don’t fully understand the attack vector, but would it be possible to identify still vulnerable users by searching for e.g. GitHub repos that have versions pinned to these older versions of these libraries or that use dependency versions that enforces a range under these versions? 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.
- robertlagrant 3y agoOWASP's DependencyTrack[0] lets you keep track of your released versions' dependencies post-release. [0] https://github.com/DependencyTrack/dependency-track https://github.com/DependencyTrack/dependency-track
- robszumski 3y agoDependencyTrack catalogs SBOMs and this is a perfect use case for them. Per parent comment, make sure your SBOM contains transitive dependencies!
- teraflop 3y agoGitHub has done exactly that for several years: https://docs.github.com/en/code-security/dependabot/dependabot-alerts/about-dependabot-alerts https://docs.github.com/en/code-security/dependabot/dependab... However, that approach will only find vulnerable dependencies in Git repositories, not ones that exist in already-published binary artifacts.