CVE-2012-2819
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 1.0% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.0% in the next 30 days (EPSS).
- Severity: 6.8 MEDIUM (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 1.0% · EPSS, next 30 days
- Weakness
- CWE-20 · Improper input validation
- Record status
- Modified
Affected
- 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
Attack profile CVSS 2.0 · 6.8
- Attack vector
- Network
- Complexity
- Medium
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
Raw vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2012-2819.md and follow it. Check whether this project is affected by CVE-2012-2819. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
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