CVE-2012-2819
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| chrome | {"endIncluding":"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
- http://code.google.com/p/chromium/issues/detail?id=120977
- http://googlechromereleases.blogspot.com/2012/06/stable-channel-update_26.html
- http://trac.webkit.org/changeset/117191
- http://trac.webkit.org/changeset/118410
- https://bugs.webkit.org/show_bug.cgi?id=85942
- https://chromiumcodereview.appspot.com/10444013
- https://hermes.opensuse.org/messages/15075728
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14938
- http://code.google.com/p/chromium/issues/detail?id=120977
- http://googlechromereleases.blogspot.com/2012/06/stable-channel-update_26.html
- http://trac.webkit.org/changeset/117191
- http://trac.webkit.org/changeset/118410
- https://bugs.webkit.org/show_bug.cgi?id=85942
- https://chromiumcodereview.appspot.com/10444013
- https://hermes.opensuse.org/messages/15075728
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14938
CWEs
CWE-20
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.