| Name | CVE-2015-1258 |
| Description | Google Chrome before 43.0.2357.65 relies on libvpx code that was not built with an appropriate --size-limit value, which allows remote attackers to trigger a negative value for a size field, and consequently cause a denial of service or possibly have unspecified other impact, via a crafted frame size in VP9 video data. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| References | DSA-3267-1 |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| libvpx (PTS) | buster | 1.7.0-3+deb10u1 | fixed |
| buster (security) | 1.7.0-3+deb10u2 | fixed |
| bullseye (security), bullseye | 1.9.0-1+deb11u2 | fixed |
| bookworm, bookworm (security) | 1.12.0-1+deb12u2 | fixed |
| sid, trixie | 1.13.1-2 | fixed |
The information below is based on the following data on fixed versions.
Notes
[wheezy] - libvpx <not-affected> (vp9 code introduced in 1.3.0)
[squeeze] - libvpx <not-affected> (vp9 code not present in 0.9.1)
That's not a vulnerability in libvpx per se
1.4.0-4 adds the workaround to configure with --size-limit=16384x16384
https://github.com/webmproject/libvpx/commit/943e43273b0a7369d07714e7fd2e19fecfb11c7c