CVE-2012-2819: Input Validation

Published Jun 27, 2012
·
Updated

The texSubImage2D implementation in the WebGL subsystem in Google Chrome before 20.0.1132.43 does not properly handle uploads to floating-point textures, which allows remote attackers to cause a denial of service (assertion failure and application crash) or possibly have unspecified other impact via a crafted web page, as demonstrated by certain WebGL performance tests, aka rdar problem 11520387.

Affected Software

43 affected components
Google Chrome<=20.0.1132.42
Google Chrome=20.0.1132.0
Google Chrome=20.0.1132.1
Google Chrome=20.0.1132.2
Google Chrome=20.0.1132.3
Google Chrome=20.0.1132.4
Google Chrome=20.0.1132.5
Google Chrome=20.0.1132.6
Google Chrome=20.0.1132.7
Google Chrome=20.0.1132.8
Google Chrome=20.0.1132.9
Google Chrome=20.0.1132.10
Google Chrome=20.0.1132.11
Google Chrome=20.0.1132.12
Google Chrome=20.0.1132.13
Google Chrome=20.0.1132.14
Google Chrome=20.0.1132.15
Google Chrome=20.0.1132.16
Google Chrome=20.0.1132.17
Google Chrome=20.0.1132.18
Google Chrome=20.0.1132.19
Google Chrome=20.0.1132.20
Google Chrome=20.0.1132.21
Google Chrome=20.0.1132.22
Google Chrome=20.0.1132.23
Google Chrome=20.0.1132.24
Google Chrome=20.0.1132.25
Google Chrome=20.0.1132.26
Google Chrome=20.0.1132.27
Google Chrome=20.0.1132.28
Google Chrome=20.0.1132.29
Google Chrome=20.0.1132.30
Google Chrome=20.0.1132.31
Google Chrome=20.0.1132.32
Google Chrome=20.0.1132.33
Google Chrome=20.0.1132.34
Google Chrome=20.0.1132.35
Google Chrome=20.0.1132.36
Google Chrome=20.0.1132.37
Google Chrome=20.0.1132.38
Google Chrome=20.0.1132.39
Google Chrome=20.0.1132.40
Google Chrome=20.0.1132.41

Event History

Jun 27, 2012
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2012-2819?

CVE-2012-2819 has a high severity rating due to its potential to cause denial of service and application crashes.

2

How do I fix CVE-2012-2819?

To fix CVE-2012-2819, update Google Chrome to version 20.0.1132.43 or later.

3

What versions of Google Chrome are affected by CVE-2012-2819?

CVE-2012-2819 affects Google Chrome versions prior to 20.0.1132.43.

4

What type of attack does CVE-2012-2819 enable?

CVE-2012-2819 could allow remote attackers to exploit the vulnerability, leading to application crashes.

5

Is there a workaround for CVE-2012-2819 if I cannot update?

There are no known workarounds for CVE-2012-2819; updating to a secure version is strongly recommended.

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