Google Chrome 21.0.1180.83 XMLHttpRequest ResourceResponse.cpp race condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Google Chrome 21.0.1180.83. This vulnerability affects unknown code of the file ResourceResponse.cpp of the component XMLHttpRequest Handler. Performing a manipulation results in race condition. This vulnerability is known as CVE-2012-2868. Furthermore, an exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as critical has been found in Google Chrome 21.0.1180.83 (Web Browser). This affects some unknown processing of the file ResourceResponse.cpp of the component XMLHttpRequest Handler. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was published 08/30/2012 by Nicolas Gregoire (miaubiz) with Google Security Team as stable-channel-update_30 as confirmed blog post (Website). It is possible to read the advisory at googlechromereleases.blogspot.com. The public release has been coordinated with Google. This vulnerability is uniquely identified as CVE-2012-2868 since 05/19/2012. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a private exploit are known.
It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 61744 (FreeBSD : chromium -- multiple vulnerabilities (ee68923d-f2f5-11e1-8014-00262d5ed8ee)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 165389 (SUSE Security Update for Chromium: Update to 21.0.1180.88 (openSUSE-SU-2012:1215-1)).
Upgrading to version 21.0.1180.89 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at trac.webkit.org. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (78177), Tenable (61744), SecurityFocus (BID 55331†), OSVDB (85033†) and Secunia (SA50447†). Similar entries are available at VDB-6071, VDB-6072, VDB-6074 and VDB-6076. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
- Product: https://www.google.com/chrome/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.4
VulDB Base Score: 7.3
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Private
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 61744
Nessus Name: FreeBSD : chromium -- multiple vulnerabilities (ee68923d-f2f5-11e1-8014-00262d5ed8ee)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
OpenVAS ID: 71827
OpenVAS Name: FreeBSD Ports: chromium
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Chrome 21.0.1180.89
Patch: trac.webkit.org
Timeline
05/19/2012 🔍08/30/2012 🔍
08/30/2012 🔍
08/30/2012 🔍
08/30/2012 🔍
08/31/2012 🔍
08/31/2012 🔍
09/03/2012 🔍
09/04/2012 🔍
03/27/2021 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: stable-channel-update_30
Researcher: Nicolas Gregoire (miaubiz)
Organization: Google Security Team
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍
CVE: CVE-2012-2868 (🔍)
GCVE (CVE): GCVE-0-2012-2868
GCVE (VulDB): GCVE-100-6075
OVAL: 🔍
X-Force: 78177 - Google Chrome XHR code execution, High Risk
SecurityFocus: 55331 - Google Chrome Prior to 21.0.1180.89 Multiple Security Vulnerabilities
Secunia: 50447 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 85033
Vulnerability Center: 36060 - Google Chrome Before 21.0.1180.89 Remote DoS or Arbitrary Code Execution Vulnerability, Medium
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 09/03/2012 11:56Updated: 03/27/2021 17:05
Changes: 09/03/2012 11:56 (93), 08/23/2017 11:51 (2), 03/27/2021 17:05 (3)
Complete: 🔍
Committer: olku
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.