CVE-2010-4203: WebM libvpx (aka the VP8 Codec SDK) before 0.9.5, as used in Google Chrome before 7.0.517.44, allows remote at
72
This week
CRITICAL 9.8REMOTEWATCHLISTUPGRADEUPGRADEMITIGATE
CVE-2010-4203 is a critical-severity flaw (CVSS 9.8) affecting chrome, libvpx, enterprise linux desktop. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
WebM libvpx (aka the VP8 Codec SDK) before 0.9.5, as used in Google Chrome before 7.0.517.44, allows remote attackers to cause a denial of service (memory corruption) or possibly execute arbitrary code via invalid frames.
Verify at the official sourceNVD · CVE Program · Report a problem with this page Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2010-4203?
chrome: upgrade to 7.0.517.44; libvpx: upgrade to 0.9.5; enterprise linux desktop: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2010-4203 being exploited?
CVE-2010-4203 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2010-4203 affect?
CVE-2010-4203 affects chrome, libvpx, enterprise linux desktop. Severity is critical (CVSS 9.8). WebM libvpx (aka the VP8 Codec SDK) before 0.9.5, as used in Google Chrome before 7.0.517.44, allows remote attackers to cause a denial of service (memory corruption) or possibly execute arbitrary code via invalid frames.
How urgent is CVE-2010-4203?
Priority 72/100. Critical severity; EPSS top 8%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist