CVE-2010-4203: Integer Overflow

Published Nov 5, 2010
·
Updated

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.

Affected Software

5 affected components
Google Chrome<7.0.517.44
webmproject libvpx<0.9.5
redhat Enterprise Linux Desktop=6.0
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Workstation=6.0

Event History

Nov 5, 2010
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2010-4203?

CVE-2010-4203 is classified as a vulnerability that can lead to denial of service or potential arbitrary code execution.

2

How do I fix CVE-2010-4203?

To fix CVE-2010-4203, update Google Chrome to version 7.0.517.44 or later and ensure you are using libvpx version 0.9.5 or higher.

3

What software is affected by CVE-2010-4203?

CVE-2010-4203 affects Google Chrome versions before 7.0.517.44 and WebM Project libvpx versions before 0.9.5.

4

Can CVE-2010-4203 lead to data breaches?

CVE-2010-4203 does not directly indicate data breaches but allows for memory corruption that could potentially lead to further exploitation.

5

Is CVE-2010-4203 still a threat today?

CVE-2010-4203 is considered less of a threat today due to the availability of patches and updates for affected software.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203