Google Chrome 57.0.2987.75 on Windows PDFium PDF File out-of-bounds write

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

Summaryinfo

A vulnerability described as critical has been identified in Google Chrome 57.0.2987.75 on Windows. The affected element is an unknown function of the component PDFium. Executing a manipulation as part of PDF File can lead to out-of-bounds write. This vulnerability is handled as CVE-2017-5032. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Google Chrome 57.0.2987.75 on Windows (Web Browser). It has been declared as critical. This vulnerability affects an unknown code block of the component PDFium. The manipulation as part of a PDF File leads to a out-of-bounds write vulnerability. The CWE definition for the vulnerability is CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

PDFium in Google Chrome prior to 57.0.2987.98 for Windows could be made to increment off the end of a buffer, which allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file.

The bug was discovered 03/09/2017. The weakness was released 04/24/2017 by Holger Fuhrmannek with Tencent (Website). The advisory is available at chromereleases.googleblog.com. This vulnerability was named CVE-2017-5032 since 01/02/2017. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 12/02/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 6 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 97783 (Debian DSA-3810-1 : chromium-browser - security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 236287 (Red Hat Update for chromium-browser Security (RHSA-2017:0499)).

Upgrading to version 57.0.2987.98 eliminates this vulnerability. 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 (97783) and SecurityFocus (BID 96767†). Entries connected to this vulnerability are available at VDB-99042, VDB-100544, VDB-100545 and VDB-100547. 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: 7.9
VulDB Meta Temp Score: 7.8

VulDB Base Score: 7.1
VulDB Temp Score: 6.8
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: Out-of-bounds write
CWE: CWE-787 / 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: 97783
Nessus Name: Debian DSA-3810-1 : chromium-browser - security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 703810
OpenVAS Name: Debian Security Advisory DSA 3810-1 (chromium-browser - security update)
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 57.0.2987.98

Timelineinfo

01/02/2017 🔍
03/09/2017 +66 days 🔍
03/09/2017 +0 days 🔍
03/15/2017 +6 days 🔍
03/17/2017 +2 days 🔍
04/24/2017 +38 days 🔍
04/24/2017 +0 days 🔍
04/25/2017 +1 days 🔍
12/02/2022 +2047 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: RHSA-2017:0499
Researcher: Holger Fuhrmannek
Organization: Tencent
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-5032 (🔍)
GCVE (CVE): GCVE-0-2017-5032
GCVE (VulDB): GCVE-100-100546

OVAL: 🔍

SecurityFocus: 96767 - Google Chrome Prior to 57.0.2987.98 Multiple Security Vulnerabilities

See also: 🔍

Entryinfo

Created: 04/25/2017 08:57
Updated: 12/02/2022 09:15
Changes: 04/25/2017 08:57 (80), 06/04/2020 17:54 (7), 12/02/2022 09:15 (4)
Complete: 🔍
Cache ID: 216::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 ▸

Might our Artificial Intelligence support you?

Check our Alexa App!