Google Chrome 22.0.1229.94 v8 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.
4.9$0-$5k0.00

Summaryinfo

A vulnerability was found in Google Chrome 22.0.1229.94. It has been classified as problematic. The impacted element is an unknown function of the component v8. The manipulation leads to memory corruption. This vulnerability is listed as CVE-2012-5128. In addition, an exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Google Chrome 22.0.1229.94 (Web Browser). It has been rated as problematic. This issue affects an unknown code block of the component v8. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Google V8 before 3.13.7.5, as used in Google Chrome before 23.0.1271.64, does not properly perform write operations, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.

The weakness was presented 11/06/2012 by Cris Neckar (Inferno) with Google Chrome Security Team as 51210 as confirmed advisory (Website). The advisory is shared at secunia.com. The public release was coordinated in cooperation with Google. The identification of this vulnerability is CVE-2012-5128 since 09/24/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 public exploit is available. No further details have been provided

It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 63361 (Fedora 17 : v8-3.13.7.5-1.fc17 (2012-20103)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks.

Upgrading to version 23.0.1271.64 eliminates this vulnerability. The upgrade is hosted for download at google.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at code.google.com. 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 (79874), Tenable (63361), SecurityFocus (BID 56413†), OSVDB (87081†) and Secunia (SA51210†). See VDB-6885, VDB-6886, VDB-6887 and VDB-6888 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 4.9

VulDB Base Score: 5.6
VulDB Temp Score: 4.9
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: Public
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 63361
Nessus Name: Fedora 17 : v8-3.13.7.5-1.fc17 (2012-20103)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

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

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Upgrade: Chrome 23.0.1271.64
Patch: code.google.com

Timelineinfo

09/24/2012 🔍
11/06/2012 +43 days 🔍
11/06/2012 +0 days 🔍
11/06/2012 +0 days 🔍
11/06/2012 +0 days 🔍
11/07/2012 +1 days 🔍
11/07/2012 +0 days 🔍
11/07/2012 +0 days 🔍
11/09/2012 +2 days 🔍
11/11/2012 +2 days 🔍
04/19/2021 +3081 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: 51210⛔
Researcher: Cris Neckar (Inferno)
Organization: Google Chrome Security Team
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2012-5128 (🔍)
GCVE (CVE): GCVE-0-2012-5128
GCVE (VulDB): GCVE-100-6893

OVAL: 🔍

X-Force: 79874 - Google Chrome code execution, High Risk
SecurityFocus: 56413 - Google Chrome Prior to 23.0.1271.64 Multiple Security Vulnerabilities
Secunia: 51210 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 87081
Vulnerability Center: 37124 - Google Chrome <23.0.1271.64 V8 Allows Remote DoS - CVE-2012-5128, Medium

See also: 🔍

Entryinfo

Created: 11/09/2012 10:16
Updated: 04/19/2021 07:43
Changes: 11/09/2012 10:16 (91), 04/20/2017 22:08 (3), 04/19/2021 07:43 (3)
Complete: 🔍
Committer:
Cache ID: 216:F3B:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!