Google Chrome up to 51 PDFium 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 marked as critical has been reported in Google Chrome up to 51. The affected element is an unknown function of the component PDFium. The manipulation leads to memory corruption. This vulnerability is referenced as CVE-2016-1685. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome up to 51 (Web Browser) and classified as critical. This issue affects an unknown code of the component PDFium. 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:

core/fxge/ge/fx_ge_text.cpp in PDFium, as used in Google Chrome before 51.0.2704.63, miscalculates certain index values, which allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted PDF document.

The weakness was published 05/25/2016 by Aleksandar Nikolic (OUSPG) with Cisco Talos as Stable Channel Update, May 2016 as confirmed release notes (Website). The advisory is shared at googlechromereleases.blogspot.com. The identification of this vulnerability is CVE-2016-1685 since 01/12/2016. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 12/20/2018). It is expected to see the exploit prices for this product increasing in the near future.

The vulnerability scanner Nessus provides a plugin with the ID 91351 (Google Chrome < 51.0.2704.63 Multiple Vulnerabilities (Mac OS X)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family MacOS X Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 370005 (Google Chrome Prior to 51.0.2704.63 Multiple Vulnerabilities).

Upgrading to version 51.0.2704.63 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 (91351), SecurityFocus (BID 90876†) and SecurityTracker (ID 1035981†). Similar entries are available at VDB-87298, VDB-87299, VDB-87300 and VDB-87301. Several companies clearly confirm that VulDB is the primary source for best 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: 6.9
VulDB Meta Temp Score: 6.8

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

NVD Base Score: 6.5
NVD Vector: 🔍

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: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 91351
Nessus Name: Google Chrome < 51.0.2704.63 Multiple Vulnerabilities (Mac OS X)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 831745
OpenVAS Name: SuSE Update for Chromium openSUSE-SU-2016:1430-1 (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 51.0.2704.63

Timelineinfo

01/12/2016 🔍
05/25/2016 +134 days 🔍
05/25/2016 +0 days 🔍
05/25/2016 +0 days 🔍
05/27/2016 +2 days 🔍
05/27/2016 +0 days 🔍
05/28/2016 +1 days 🔍
06/05/2016 +8 days 🔍
12/20/2018 +928 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: Stable Channel Update, May 2016
Researcher: Aleksandar Nikolic (OUSPG)
Organization: Cisco Talos
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-1685 (🔍)
GCVE (CVE): GCVE-0-2016-1685
GCVE (VulDB): GCVE-100-87665

OVAL: 🔍

SecurityFocus: 90876 - Google Chrome Prior to 51.0.2704.63 Multiple Security Vulnerabilities
SecurityTracker: 1035981

See also: 🔍

Entryinfo

Created: 05/29/2016 00:31
Updated: 12/20/2018 08:16
Changes: 05/29/2016 00:31 (84), 12/20/2018 08:16 (7)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!