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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade libvpx | Jul 30, 2024 | May 20, 2015 |
| Freebsd | — | Upgrade chromiumUpgrade chromium-pulseUpgrade chromium-npapi | Dec 10, 2025 | May 19, 2015 |
| Gentoo Linux | — | Upgrade www-client/chromium. | Oct 30, 2017 | May 20, 2015 |
| Google Chrome | — | Upgrade to the latest version of Google Chrome | May 22, 2015 | May 19, 2015 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | May 19, 2015 |
| Suse | — | Upgrade chromium | Dec 18, 2015 | May 20, 2015 |
| Ubuntu | — | Upgrade oxideqt-codecsUpgrade liboxideqtcore0Upgrade oxideqt-codecs-extra | Nov 8, 2024 | May 20, 2015 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub