Google Chrome prior 61.0.3163.113 on Chrome OS Crash Reporting HTML Page access control

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.7$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Google Chrome on Chrome OS. This impacts an unknown function of the component Crash Reporting. This manipulation as part of HTML Page causes access control. This vulnerability is tracked as CVE-2017-15404. The attack is restricted to local execution. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome on Chrome OS (Web Browser). It has been declared as critical. Affected by this vulnerability is an unknown code of the component Crash Reporting. The manipulation as part of a HTML Page leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

An ability to process crash dumps under root privileges and inappropriate symlinks handling could lead to a local privilege escalation in Crash Reporting in Google Chrome on Chrome OS prior to 61.0.3163.113 allowed a local attacker to perform privilege escalation via a crafted HTML page.

The bug was discovered 10/05/2017. The weakness was disclosed 01/09/2019 (Website). The advisory is shared at chromereleases.googleblog.com. This vulnerability is known as CVE-2017-15404 since 10/17/2017. An attack has to be approached locally. A single authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 461 days. During that time the estimated underground price was around $25k-$100k.

Upgrading to version 61.0.3163.113 eliminates this vulnerability.

The entries VDB-128796 and VDB-128798 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.0
VulDB Meta Temp Score: 6.9

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

NVD Base Score: 7.8
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Chrome 61.0.3163.113

Timelineinfo

10/05/2017 🔍
10/17/2017 +12 days 🔍
01/09/2019 +449 days 🔍
01/09/2019 +0 days 🔍
01/10/2019 +1 days 🔍
04/26/2020 +472 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: chromereleases.googleblog.com
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-15404 (🔍)
GCVE (CVE): GCVE-0-2017-15404
GCVE (VulDB): GCVE-100-128797
See also: 🔍

Entryinfo

Created: 01/10/2019 07:42
Updated: 04/26/2020 21:03
Changes: 01/10/2019 07:42 (64), 04/26/2020 21:03 (2)
Complete: 🔍
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 ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!