Google Chrome 21.0.1180.83 memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.6$5k-$25k0.00

Summaryinfo

A vulnerability classified as problematic was found in Google Chrome 21.0.1180.83. This issue affects some unknown processing. Executing a manipulation can lead to memory corruption. This vulnerability is handled as CVE-2012-2869. Additionally, an exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as critical was found in Google Chrome 21.0.1180.83 (Web Browser). This vulnerability affects an unknown function. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Google Chrome before 21.0.1180.89 does not properly load URLs, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that trigger a "stale buffer."

The weakness was released 08/30/2012 by Fermin Serna (miaubiz) with Google Security Team as stable-channel-update_30 as not defined blog post (Website). The advisory is shared for download at googlechromereleases.blogspot.com. The public release was coordinated with the vendor. This vulnerability was named CVE-2012-2869 since 05/19/2012. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are unknown but a private exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 04/16/2017). It is expected to see the exploit prices for this product increasing in the near future.

It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 802451 , which helps to determine the existence of the flaw in a target environment. 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. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (78178), Tenable (802451), SecurityFocus (BID 55331†), OSVDB (85034†) and Secunia (SA50447†). Entries connected to this vulnerability are available at VDB-6071, VDB-6072, VDB-6074 and VDB-6075. Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.6

VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 802451
Nessus File: 🔍
Nessus Risk: 🔍

OpenVAS ID: 71827
OpenVAS Name: FreeBSD Ports: chromium
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Chrome 21.0.1180.89

Timelineinfo

05/19/2012 🔍
08/30/2012 +103 days 🔍
08/30/2012 +0 days 🔍
08/30/2012 +0 days 🔍
08/30/2012 +0 days 🔍
08/31/2012 +1 days 🔍
08/31/2012 +0 days 🔍
08/31/2012 +0 days 🔍
09/03/2012 +3 days 🔍
09/03/2012 +0 days 🔍
09/04/2012 +1 days 🔍
04/16/2017 +1685 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: stable-channel-update_30
Researcher: Fermin Serna (miaubiz)
Organization: Google Security Team
Status: Not defined
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2012-2869 (🔍)
GCVE (CVE): GCVE-0-2012-2869
GCVE (VulDB): GCVE-100-6076

OVAL: 🔍

X-Force: 78178
SecurityFocus: 55331 - Google Chrome Prior to 21.0.1180.89 Multiple Security Vulnerabilities
Secunia: 50447 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 85034
Vulnerability Center: 36061 - Google Chrome Before 21.0.1180.89 Remote DoS Vulnerability via Vectors That Trigger a \, Medium

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 09/03/2012 12:29
Updated: 04/16/2017 11:24
Changes: 09/03/2012 12:29 (78), 04/16/2017 11:24 (11)
Complete: 🔍
Committer: olku
Cache ID: 216:5F4:103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!