Google Chrome up to 54 PDFium use after free

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.
7.4$5k-$25k0.00

Summaryinfo

A vulnerability was found in Google Chrome up to 54 and classified as critical. Affected is an unknown function of the component PDFium. Executing a manipulation can lead to use after free. This vulnerability appears as CVE-2016-5183. The attack may be performed from remote. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome up to 54 (Web Browser). It has been declared as critical. This vulnerability affects an unknown code of the component PDFium. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

A heap use after free in PDFium in Google Chrome prior to 54.0.2840.59 for Windows, Mac, and Linux; 54.0.2840.85 for Android allows a remote attacker to potentially exploit heap corruption via crafted PDF files.

The bug was discovered 10/12/2016. The weakness was presented 12/18/2016 by Abdulrahman Alqabandi (Cloudfuzzer) with Tencent (Website). The advisory is shared for download at securityfocus.com. This vulnerability was named CVE-2016-5183 since 05/31/2016. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 10/12/2022). It is expected to see the exploit prices for this product increasing in the near future.

The vulnerability was handled as a non-public zero-day exploit for at least 28 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 94661 (Fedora 24 : 1:chromium-native_client / chromium (2016-c671aae490)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 370162 (Google Chrome Prior to 54.0.2840.59 Multiple Vulnerabilities).

Upgrading to version 54.0.2840.59 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (94661) and SecurityFocus (BID 93528†). See VDB-93280, VDB-94586, VDB-94587 and VDB-94589 for similar entries. Once again VulDB remains the best source for 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: 7.6
VulDB Meta Temp Score: 7.4

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

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

NVD Base Score: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / 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: 94661
Nessus Name: Fedora 24 : 1:chromium-native_client / chromium (2016-c671aae490)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 54318
OpenVAS Name: Fedora Update for chromium FEDORA-2016-c671aae490
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Chrome 54.0.2840.59

Timelineinfo

05/31/2016 🔍
10/12/2016 +134 days 🔍
10/12/2016 +0 days 🔍
11/09/2016 +28 days 🔍
11/10/2016 +1 days 🔍
12/17/2016 +37 days 🔍
12/18/2016 +1 days 🔍
12/18/2016 +0 days 🔍
10/12/2022 +2124 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: FEDORA-2016-c671aae490⛔
Researcher: Abdulrahman Alqabandi (Cloudfuzzer)
Organization: Tencent
Status: Not defined
Confirmation: 🔍

CVE: CVE-2016-5183 (🔍)
GCVE (CVE): GCVE-0-2016-5183
GCVE (VulDB): GCVE-100-94588

OVAL: 🔍

SecurityFocus: 93528 - Google Chrome Prior to 54.0.2840.59 Multiple Security Vulnerabilities

See also: 🔍

Entryinfo

Created: 12/18/2016 16:04
Updated: 10/12/2022 09:32
Changes: 12/18/2016 16:04 (78), 07/09/2019 18:10 (9), 10/12/2022 09:28 (3), 10/12/2022 09:32 (1)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!