Google Chrome 23.0.1271.97 PDF Image 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.
8.9$0-$5k0.00

Summaryinfo

A vulnerability has been found in Google Chrome 23.0.1271.97 and classified as critical. Affected is an unknown function of the component PDF Image Handler. The manipulation leads to memory corruption. This vulnerability is referenced as CVE-2012-5157. Furthermore, an exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Google Chrome 23.0.1271.97 (Web Browser). It has been rated as critical. This issue affects an unknown part of the component PDF Image Handler. 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 Chrome before 24.0.1312.52 does not properly handle image data in PDF documents, which allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted document.

The weakness was published 01/10/2013 by Mateusz Jurczyk and Gynvael Coldwind (Inferno) with Google Security Team as 162156 as confirmed advisory (Website). The advisory is shared at code.google.com. The public release has been coordinated with Google. The identification of this vulnerability is CVE-2012-5157 since 09/24/2012. The exploitation is known to be difficult. The attack may be initiated remotely. A simple authentication is necessary for exploitation. Technical details are unknown but a public exploit is available.

It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $100k and more. The vulnerability scanner Nessus provides a plugin with the ID 63469 (FreeBSD : chromium -- multiple vulnerabilities (46bd747b-5b84-11e2-b06d-00262d5ed8ee)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 120803 (Google Chrome Prior to 24.0.1312.52 Multiple Vulnerabilities).

Upgrading to version 24.0.1312.52 eliminates this vulnerability. The upgrade is hosted for download at 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 (63469), SecurityFocus (BID 57251†), OSVDB (89083†), Secunia (SA51825†) and SecurityTracker (ID 1027977†). Similar entries are available at VDB-7314, VDB-7315, VDB-7316 and VDB-7317. 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: 9.9
VulDB Meta Temp Score: 8.9

VulDB Base Score: 9.9
VulDB Temp Score: 8.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: 63469
Nessus Name: FreeBSD : chromium -- multiple vulnerabilities (46bd747b-5b84-11e2-b06d-00262d5ed8ee)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 803158
OpenVAS Name: Google Chrome Multiple Vulnerabilities-01 Jan2013 (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 24.0.1312.52

Timelineinfo

09/24/2012 🔍
01/10/2013 +108 days 🔍
01/10/2013 +0 days 🔍
01/10/2013 +0 days 🔍
01/11/2013 +1 days 🔍
01/11/2013 +0 days 🔍
01/12/2013 +1 days 🔍
01/15/2013 +3 days 🔍
01/15/2013 +0 days 🔍
05/02/2018 +1933 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: 162156
Researcher: Mateusz Jurczyk, Gynvael Coldwind (Inferno)
Organization: Google Security Team
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2012-5157 (🔍)
GCVE (CVE): GCVE-0-2012-5157
GCVE (VulDB): GCVE-100-7325

OVAL: 🔍

SecurityFocus: 57251
Secunia: 51825 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 89083
SecurityTracker: 1027977

See also: 🔍

Entryinfo

Created: 01/15/2013 14:44
Updated: 05/02/2018 09:22
Changes: 01/15/2013 14:44 (80), 05/02/2018 09:22 (7)
Complete: 🔍
Committer:
Cache ID: 216::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 ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!