CVE-2012-2819
Last modified
CVE-2012-2819 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.98% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | <= 20.0.1132.42 | |
| Chrome | 20.0.1132.0 | |
| Chrome | 20.0.1132.1 | |
| Chrome | 20.0.1132.2 | |
| Chrome | 20.0.1132.3 | |
| Chrome | 20.0.1132.4 | |
| Chrome | 20.0.1132.5 | |
| Chrome | 20.0.1132.6 | |
| Chrome | 20.0.1132.7 | |
| Chrome | 20.0.1132.8 | |
| Chrome | 20.0.1132.9 | |
| Chrome | 20.0.1132.10 | |
| Chrome | 20.0.1132.11 | |
| Chrome | 20.0.1132.12 | |
| Chrome | 20.0.1132.13 | |
| Chrome | 20.0.1132.14 | |
| Chrome | 20.0.1132.15 | |
| Chrome | 20.0.1132.16 | |
| Chrome | 20.0.1132.17 | |
| Chrome | 20.0.1132.18 | |
| Chrome | 20.0.1132.19 | |
| Chrome | 20.0.1132.20 | |
| Chrome | 20.0.1132.21 | |
| Chrome | 20.0.1132.22 | |
| Chrome | 20.0.1132.23 | |
| Chrome | 20.0.1132.24 | |
| Chrome | 20.0.1132.25 | |
| Chrome | 20.0.1132.26 | |
| Chrome | 20.0.1132.27 | |
| Chrome | 20.0.1132.28 | |
| Chrome | 20.0.1132.29 | |
| Chrome | 20.0.1132.30 | |
| Chrome | 20.0.1132.31 | |
| Chrome | 20.0.1132.32 | |
| Chrome | 20.0.1132.33 | |
| Chrome | 20.0.1132.34 | |
| Chrome | 20.0.1132.35 | |
| Chrome | 20.0.1132.36 | |
| Chrome | 20.0.1132.37 | |
| Chrome | 20.0.1132.38 | |
| Chrome | 20.0.1132.39 | |
| Chrome | 20.0.1132.40 | |
| Chrome | 20.0.1132.41 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2012-2819?
How severe is CVE-2012-2819?
How do I fix CVE-2012-2819?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2012
- CVE-2012-2813The exif_convert_utf16_to_utf8 function in exif-entry.c in t…
- CVE-2012-2814Buffer overflow in the exif_entry_format_value function in e…
- CVE-2012-2815Google Chrome before 20.0.1132.43 allows remote attackers to…
- CVE-2012-2816Google Chrome before 20.0.1132.43 on Windows does not proper…
- CVE-2012-2817Use-after-free vulnerability in Google Chrome before 20.0.11…
- CVE-2012-2818Use-after-free vulnerability in Google Chrome before 20.0.11…
- CVE-2012-2820Google Chrome before 20.0.1132.43 does not properly implemen…
- CVE-2012-2821The autofill implementation in Google Chrome before 20.0.113…
- CVE-2012-2822The PDF functionality in Google Chrome before 20.0.1132.43 a…
- CVE-2012-2823Use-after-free vulnerability in Google Chrome before 20.0.11…
- CVE-2012-2824Use-after-free vulnerability in Google Chrome before 20.0.11…
- CVE-2012-2825The XSL implementation in Google Chrome before 20.0.1132.43 …
Are you affected by CVE-2012-2819?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
