Google Chrome up to 23.0.1271.96 History Navigation code injection

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.
8.5$0-$5k0.00

A vulnerability, which was classified as critical, has been found in Google Chrome up to 23.0.1271.96 (Web Browser). Affected by this issue is an unknown code block of the component History Navigation Handler. The manipulation with an unknown input leads to a code injection vulnerability. Using CWE to declare the problem leads to CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Impacted is confidentiality, integrity, and availability. CVE summarizes:

Google Chrome before 23.0.1271.97 does not properly handle history navigation, which allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via unspecified vectors.

The bug was discovered 12/11/2012. The weakness was released 12/11/2012 by Michal Zalewski (pawlkt) with Google Security Team as confirmed changelog entry (Website). The advisory is available at googlechromereleases.blogspot.dk. The public release was coordinated with the vendor. This vulnerability is handled as CVE-2012-5142 since 09/24/2012. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are unknown but a public exploit is available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 04/20/2021). It is expected to see the exploit prices for this product increasing in the near future.This vulnerability is assigned to T1059 by the MITRE ATT&CK project.

The vulnerability was handled as a non-public zero-day exploit for at least 15685 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 63256 (FreeBSD : chromium -- multiple vulnerabilities (51f84e28-444e-11e2-8306-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 120725 (Google Chrome Prior to 23.0.1271.97 Multiple Vulnerabilities).

Upgrading to version 23.0.1271.97 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 (80634) and Tenable (63256). Entries connected to this vulnerability are available at 7163, 7164, 7165 and 7167.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB CVSS-B Score: 🔍
VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.8
VulDB Meta Temp Score: 8.5

VulDB Base Score: 9.8
VulDB Temp Score: 8.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

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

NVD Base Score: 🔍

Exploitinginfo

Class: Code injection
CWE: CWE-94 / CWE-74 / CWE-707
ATT&CK: T1059

Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Unproven

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Nessus ID: 63256
Nessus Name: FreeBSD : chromium -- multiple vulnerabilities (51f84e28-444e-11e2-8306-00262d5ed8ee)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 803128
OpenVAS Name: Google Chrome Multiple Vulnerabilities-03 Dec2012 (Linux)
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 23.0.1271.97

Timelineinfo

09/24/2012 🔍
12/11/2012 +78 days 🔍
12/11/2012 +0 days 🔍
12/11/2012 +0 days 🔍
12/11/2012 +0 days 🔍
12/12/2012 +1 days 🔍
12/12/2012 +0 days 🔍
12/17/2012 +5 days 🔍
12/17/2012 +0 days 🔍
04/20/2021 +3046 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: googlechromereleases.blogspot.dk
Researcher: Michal Zalewski (pawlkt)
Organization: Google Security Team
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2012-5142 (🔍)
OVAL: 🔍

X-Force: 80634 - Google Chrome history navigation denial of service, Medium Risk
Vulnerability Center: 37696 - Google Chrome Before 23.0.1271.97 Mishandle History Navigation Remote Code Execution Vulnerability, Medium
SecurityFocus: 56903
Secunia: 51549 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 88376

See also: 🔍

Entryinfo

Created: 12/17/2012 14:53
Updated: 04/20/2021 11:11
Changes: 12/17/2012 14:53 (90), 04/22/2017 17:12 (1), 04/20/2021 11:11 (3)
Complete: 🔍
Committer:

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!