Google Chrome up to 56 Skia 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.0$5k-$25k0.00

Summaryinfo

A vulnerability classified as critical has been found in Google Chrome up to 56. Affected by this issue is some unknown functionality of the component Skia. The manipulation leads to memory corruption. This vulnerability is listed as CVE-2017-5014. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

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

Heap buffer overflow during image processing in Skia in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page.

The bug was discovered 01/25/2017. The weakness was presented 01/25/2017 by Armin Razmdjou (Paul) with Tresorit as Stable Channel Update for Desktop, January 2017 as confirmed release notes (Website). The advisory is shared at chromereleases.googleblog.com. The identification of this vulnerability is CVE-2017-5014 since 01/02/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. 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 08/04/2020). 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 96852 (GLSA-201701-66 : Chromium: Multiple vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Gentoo Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 236251 (Red Hat Update forchromium-browser Security (RHSA-2017:0206)).

Upgrading to version 56.0.2924.76 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (96852), SecurityFocus (BID 95792†) and SecurityTracker (ID 1037718†). See VDB-96042, VDB-96043, VDB-96044 and VDB-96045 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 6.1

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

NVD Base Score: 6.3
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: 96852
Nessus Name: GLSA-201701-66 : Chromium: Multiple vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 703776
OpenVAS Name: Debian Security Advisory DSA 3776-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: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Chrome 56.0.2924.76

Timelineinfo

01/02/2017 🔍
01/25/2017 +23 days 🔍
01/25/2017 +0 days 🔍
01/25/2017 +0 days 🔍
01/25/2017 +0 days 🔍
01/26/2017 +1 days 🔍
01/27/2017 +1 days 🔍
01/30/2017 +3 days 🔍
02/17/2017 +18 days 🔍
08/04/2020 +1264 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: Stable Channel Update for Desktop, January 2017
Researcher: Armin Razmdjou (Paul)
Organization: Tresorit
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-5014 (🔍)
GCVE (CVE): GCVE-0-2017-5014
GCVE (VulDB): GCVE-100-96053

OVAL: 🔍

SecurityFocus: 95792 - Google Chrome Multiple Security Vulnerabilities
OSVDB: - CVE-2017-5014 - Google - Chrome - Buffer Overflow Issue
SecurityTracker: 1037718

See also: 🔍

Entryinfo

Created: 01/27/2017 12:22
Updated: 08/04/2020 09:38
Changes: 01/27/2017 12:22 (83), 08/04/2020 09:38 (9)
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!