Google Chrome up to 20.0.1132.57 Downloader resource management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Chrome up to 20.0.1132.57. It has been classified as critical. Affected by this vulnerability is an unknown functionality of the component Downloader. The manipulation leads to resource management. This vulnerability is referenced as CVE-2012-2847. Furthermore, an exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Google Chrome up to 20.0.1132.57 (Web Browser). It has been rated as critical. This issue affects an unknown code block of the component Downloader. The manipulation with an unknown input leads to a resource management vulnerability. Using CWE to declare the problem leads to CWE-399. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Google Chrome before 21.0.1180.57 on Mac OS X and Linux, and before 21.0.1180.60 on Windows and Chrome Frame, does not request user confirmation before continuing a large series of downloads, which allows user-assisted remote attackers to cause a denial of service (resource consumption) via a crafted web site.
The weakness was published 07/31/2012 by Matt Austin (OUSPG) with Aspect Security as Stable Channel Release as not defined changelog entry (Website). The advisory is shared at googlechromereleases.blogspot.ch. The public release has been coordinated with Google. The identification of this vulnerability is CVE-2012-2847 since 05/19/2012. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a private exploit is available.
It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 61381 (Google Chrome < 21.0.1180.60 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows.
Upgrading to version 21.0.1180.57 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (61381), SecurityFocus (BID 54749†), OSVDB (84367†), Secunia (SA50105†) and Vulnerability Center (SBV-35897†). Similar entries are available at VDB-5884, VDB-5886, VDB-5887 and VDB-5888. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 20.0.1132.0
- 20.0.1132.1
- 20.0.1132.2
- 20.0.1132.3
- 20.0.1132.4
- 20.0.1132.5
- 20.0.1132.6
- 20.0.1132.7
- 20.0.1132.8
- 20.0.1132.9
- 20.0.1132.10
- 20.0.1132.11
- 20.0.1132.12
- 20.0.1132.13
- 20.0.1132.14
- 20.0.1132.15
- 20.0.1132.16
- 20.0.1132.17
- 20.0.1132.18
- 20.0.1132.19
- 20.0.1132.20
- 20.0.1132.21
- 20.0.1132.22
- 20.0.1132.23
- 20.0.1132.24
- 20.0.1132.25
- 20.0.1132.26
- 20.0.1132.27
- 20.0.1132.28
- 20.0.1132.29
- 20.0.1132.30
- 20.0.1132.31
- 20.0.1132.32
- 20.0.1132.33
- 20.0.1132.34
- 20.0.1132.35
- 20.0.1132.36
- 20.0.1132.37
- 20.0.1132.38
- 20.0.1132.39
- 20.0.1132.40
- 20.0.1132.41
- 20.0.1132.42
- 20.0.1132.43
- 20.0.1132.44
- 20.0.1132.45
- 20.0.1132.46
- 20.0.1132.47
- 20.0.1132.48
- 20.0.1132.49
- 20.0.1132.50
- 20.0.1132.51
- 20.0.1132.52
- 20.0.1132.53
- 20.0.1132.54
- 20.0.1132.55
- 20.0.1132.56
- 20.0.1132.57
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: 10.0VulDB Meta Temp Score: 9.0
VulDB Base Score: 10.0
VulDB Temp Score: 9.0
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: Resource managementCWE: CWE-399 / CWE-404
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: 61381
Nessus Name: Google Chrome < 21.0.1180.60 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
OpenVAS ID: 71505
OpenVAS Name: FreeBSD Ports: chromium
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Chrome 21.0.1180.57
Timeline
05/19/2012 🔍06/08/2012 🔍
07/31/2012 🔍
07/31/2012 🔍
07/31/2012 🔍
08/01/2012 🔍
08/01/2012 🔍
08/01/2012 🔍
08/06/2012 🔍
08/09/2012 🔍
08/16/2012 🔍
03/27/2021 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: Stable Channel Release
Researcher: Matt Austin (OUSPG)
Organization: Aspect Security
Status: Not defined
Confirmation: 🔍
Coordinated: 🔍
CVE: CVE-2012-2847 (🔍)
GCVE (CVE): GCVE-0-2012-2847
GCVE (VulDB): GCVE-100-5885
OVAL: 🔍
SecurityFocus: 54749 - Google Chrome Prior to 21 Multiple Security Vulnerabilities
Secunia: 50105 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 84367
Vulnerability Center: 35897 - Google Chrome Before 21.0.1180.57 and Before 21.0.1180.60 Remote DoS Vulnerability, Medium
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 08/09/2012 13:17Updated: 03/27/2021 08:22
Changes: 08/09/2012 13:17 (79), 04/15/2017 16:33 (11), 03/27/2021 08:22 (3)
Complete: 🔍
Cache ID: 216:883:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.