Google Chrome 19.0.1084.51 PDF Viewer 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.
9.0$0-$5k0.00

Summaryinfo

A vulnerability described as critical has been identified in Google Chrome 19.0.1084.51. This issue affects some unknown processing of the component PDF Viewer. Executing a manipulation can lead to memory corruption. This vulnerability is registered as CVE-2011-3110. Furthermore, an exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as critical was found in Google Chrome 19.0.1084.51 (Web Browser). This vulnerability affects an unknown code block of the component PDF Viewer. 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:

The PDF functionality in Google Chrome before 19.0.1084.52 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that trigger out-of-bounds write operations.

The weakness was published 05/23/2012 by Matthew Jurczyk and Gynvael Coldwind (efbiaiinzinz) with Google Security Team as confirmed changelog entry (Website). The advisory is available at googlechromereleases.blogspot.ch. This vulnerability was named CVE-2011-3110 since 08/09/2011. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are unknown but a public exploit is available.

It is declared as proof-of-concept. As 0-day the estimated underground price was around $100k and more. The vulnerability scanner Nessus provides a plugin with the ID 59281 (FreeBSD : chromium -- multiple vulnerabilities (219d0bfd-a915-11e1-b519-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 120235 (Google Chrome prior to 19.0.1084.52 Multiple Vulnerabilities).

Upgrading to version 19.0.1084.52 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 (59281), SecurityFocus (BID 53679†), OSVDB (93226†), Secunia (SA49277†) and SecurityTracker (ID 1027098†). Similar entries are available at VDB-5448, VDB-5449, VDB-5450 and VDB-5451. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 9.0

VulDB Base Score: 10.0
VulDB Temp Score: 9.0
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: 59281
Nessus Name: FreeBSD : chromium -- multiple vulnerabilities (219d0bfd-a915-11e1-b519-00262d5ed8ee)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 71365
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 19.0.1084.52

Timelineinfo

08/09/2011 🔍
05/23/2012 +288 days 🔍
05/23/2012 +0 days 🔍
05/24/2012 +1 days 🔍
05/24/2012 +0 days 🔍
05/24/2012 +0 days 🔍
05/24/2012 +0 days 🔍
05/29/2012 +5 days 🔍
05/14/2013 +350 days 🔍
05/06/2018 +1818 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: googlechromereleases.blogspot.ch
Researcher: Matthew Jurczyk, Gynvael Coldwind (efbiaiinzinz)
Organization: Google Security Team
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2011-3110 (🔍)
GCVE (CVE): GCVE-0-2011-3110
GCVE (VulDB): GCVE-100-8650

OVAL: 🔍

SecurityFocus: 53679
Secunia: 49277 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 93226
SecurityTracker: 1027098

See also: 🔍

Entryinfo

Created: 05/14/2013 15:56
Updated: 05/06/2018 11:18
Changes: 05/14/2013 15:56 (78), 05/06/2018 11:18 (7)
Complete: 🔍
Committer:
Cache ID: 216:489:103

If you want to get best quality of vulnerability data, you may have to visit 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!