CVE-2012-2868: Race Condition
First published: Fri Aug 31 2012(Updated: )
Race condition in Google Chrome before 21.0.1180.89 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors involving improper interaction between worker processes and an XMLHttpRequest (aka XHR) object.
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| SUSE Linux | =12.1 | |
| SUSE Linux | =12.2 | |
| Google Chrome (Trace Event) | <=21.0.1180.88 | |
| Google Chrome (Trace Event) | =21.0.1180.0 | |
| Google Chrome (Trace Event) | =21.0.1180.1 | |
| Google Chrome (Trace Event) | =21.0.1180.2 | |
| Google Chrome (Trace Event) | =21.0.1180.31 | |
| Google Chrome (Trace Event) | =21.0.1180.32 | |
| Google Chrome (Trace Event) | =21.0.1180.33 | |
| Google Chrome (Trace Event) | =21.0.1180.34 | |
| Google Chrome (Trace Event) | =21.0.1180.35 | |
| Google Chrome (Trace Event) | =21.0.1180.36 | |
| Google Chrome (Trace Event) | =21.0.1180.37 | |
| Google Chrome (Trace Event) | =21.0.1180.38 | |
| Google Chrome (Trace Event) | =21.0.1180.39 | |
| Google Chrome (Trace Event) | =21.0.1180.41 | |
| Google Chrome (Trace Event) | =21.0.1180.46 | |
| Google Chrome (Trace Event) | =21.0.1180.47 | |
| Google Chrome (Trace Event) | =21.0.1180.48 | |
| Google Chrome (Trace Event) | =21.0.1180.49 | |
| Google Chrome (Trace Event) | =21.0.1180.50 | |
| Google Chrome (Trace Event) | =21.0.1180.51 | |
| Google Chrome (Trace Event) | =21.0.1180.52 | |
| Google Chrome (Trace Event) | =21.0.1180.53 | |
| Google Chrome (Trace Event) | =21.0.1180.54 | |
| Google Chrome (Trace Event) | =21.0.1180.55 | |
| Google Chrome (Trace Event) | =21.0.1180.56 | |
| Google Chrome (Trace Event) | =21.0.1180.57 | |
| Google Chrome (Trace Event) | =21.0.1180.59 | |
| Google Chrome (Trace Event) | =21.0.1180.60 | |
| Google Chrome (Trace Event) | =21.0.1180.61 | |
| Google Chrome (Trace Event) | =21.0.1180.62 | |
| Google Chrome (Trace Event) | =21.0.1180.63 | |
| Google Chrome (Trace Event) | =21.0.1180.64 | |
| Google Chrome (Trace Event) | =21.0.1180.68 | |
| Google Chrome (Trace Event) | =21.0.1180.69 | |
| Google Chrome (Trace Event) | =21.0.1180.70 | |
| Google Chrome (Trace Event) | =21.0.1180.71 | |
| Google Chrome (Trace Event) | =21.0.1180.72 | |
| Google Chrome (Trace Event) | =21.0.1180.73 | |
| Google Chrome (Trace Event) | =21.0.1180.74 | |
| Google Chrome (Trace Event) | =21.0.1180.75 | |
| Google Chrome (Trace Event) | =21.0.1180.76 | |
| Google Chrome (Trace Event) | =21.0.1180.77 | |
| Google Chrome (Trace Event) | =21.0.1180.78 | |
| Google Chrome (Trace Event) | =21.0.1180.79 | |
| Google Chrome (Trace Event) | =21.0.1180.80 | |
| Google Chrome (Trace Event) | =21.0.1180.81 | |
| Google Chrome (Trace Event) | =21.0.1180.82 | |
| Google Chrome (Trace Event) | =21.0.1180.83 | |
| Google Chrome (Trace Event) | =21.0.1180.84 | |
| Google Chrome (Trace Event) | =21.0.1180.85 | |
| Google Chrome (Trace Event) | =21.0.1180.86 | |
| Google Chrome (Trace Event) | =21.0.1180.87 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://code.google.com/p/chromium/issues/detail?id=136881
- http://googlechromereleases.blogspot.com/2012/08/stable-channel-update_30.html
- http://lists.opensuse.org/opensuse-security-announce/2012-09/msg00030.html
- http://osvdb.org/85033
- https://exchange.xforce.ibmcloud.com/vulnerabilities/78177
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A15842
Frequently Asked Questions
What is the severity of CVE-2012-2868?
CVE-2012-2868 has been classified as a high severity vulnerability due to its potential to cause denial of service.
How do I fix CVE-2012-2868?
To mitigate CVE-2012-2868, upgrade Google Chrome to version 21.0.1180.89 or later.
What does CVE-2012-2868 exploit?
CVE-2012-2868 exploits a race condition involving worker processes and XMLHttpRequest objects.
What versions of Google Chrome are affected by CVE-2012-2868?
CVE-2012-2868 affects Google Chrome versions before 21.0.1180.89.
Is CVE-2012-2868 present in OpenSUSE?
Yes, CVE-2012-2868 can affect OpenSUSE versions 12.1 and 12.2 when using vulnerable versions of Google Chrome.
- agent/references
- agent/type
- agent/last-modified-date
- agent/first-publish-date
- agent/author
- agent/severity
- agent/weakness
- agent/remedy
- agent/description
- agent/event
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/opensuse
- canonical/suse linux
- version/suse linux/12.1
- version/suse linux/12.2
- vendor/google
- canonical/google chrome (trace event)
- version/google chrome (trace event)/21.0.1180.88
- version/google chrome (trace event)/21.0.1180.0
- version/google chrome (trace event)/21.0.1180.1
- version/google chrome (trace event)/21.0.1180.2
- version/google chrome (trace event)/21.0.1180.31
- version/google chrome (trace event)/21.0.1180.32
- version/google chrome (trace event)/21.0.1180.33
- version/google chrome (trace event)/21.0.1180.34
- version/google chrome (trace event)/21.0.1180.35
- version/google chrome (trace event)/21.0.1180.36
- version/google chrome (trace event)/21.0.1180.37
- version/google chrome (trace event)/21.0.1180.38
- version/google chrome (trace event)/21.0.1180.39
- version/google chrome (trace event)/21.0.1180.41
- version/google chrome (trace event)/21.0.1180.46
- version/google chrome (trace event)/21.0.1180.47
- version/google chrome (trace event)/21.0.1180.48
- version/google chrome (trace event)/21.0.1180.49
- version/google chrome (trace event)/21.0.1180.50
- version/google chrome (trace event)/21.0.1180.51
- version/google chrome (trace event)/21.0.1180.52
- version/google chrome (trace event)/21.0.1180.53
- version/google chrome (trace event)/21.0.1180.54
- version/google chrome (trace event)/21.0.1180.55
- version/google chrome (trace event)/21.0.1180.56
- version/google chrome (trace event)/21.0.1180.57
- version/google chrome (trace event)/21.0.1180.59
- version/google chrome (trace event)/21.0.1180.60
- version/google chrome (trace event)/21.0.1180.61
- version/google chrome (trace event)/21.0.1180.62
- version/google chrome (trace event)/21.0.1180.63
- version/google chrome (trace event)/21.0.1180.64
- version/google chrome (trace event)/21.0.1180.68
- version/google chrome (trace event)/21.0.1180.69
- version/google chrome (trace event)/21.0.1180.70
- version/google chrome (trace event)/21.0.1180.71
- version/google chrome (trace event)/21.0.1180.72
- version/google chrome (trace event)/21.0.1180.73
- version/google chrome (trace event)/21.0.1180.74
- version/google chrome (trace event)/21.0.1180.75
- version/google chrome (trace event)/21.0.1180.76
- version/google chrome (trace event)/21.0.1180.77
- version/google chrome (trace event)/21.0.1180.78
- version/google chrome (trace event)/21.0.1180.79
- version/google chrome (trace event)/21.0.1180.80
- version/google chrome (trace event)/21.0.1180.81
- version/google chrome (trace event)/21.0.1180.82
- version/google chrome (trace event)/21.0.1180.83
- version/google chrome (trace event)/21.0.1180.84
- version/google chrome (trace event)/21.0.1180.85
- version/google chrome (trace event)/21.0.1180.86
- version/google chrome (trace event)/21.0.1180.87