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

Summaryinfo

A vulnerability was found in Google Chrome up to 56 and classified as critical. This vulnerability affects unknown code of the component Omnibox. Such manipulation leads to access control (Address). This vulnerability is traded as CVE-2017-5015. The attack may be launched remotely. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome up to 56 (Web Browser) and classified as critical. Affected by this issue is an unknown code of the component Omnibox. The manipulation with an unknown input leads to a access control vulnerability (Address). Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. CVE summarizes:

Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, incorrectly handled Unicode glyphs, which allowed a remote attacker to perform domain spoofing via IDN homographs in a crafted domain name.

The bug was discovered 01/25/2017. The weakness was shared 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 for download at chromereleases.googleblog.com. This vulnerability is handled as CVE-2017-5015 since 01/02/2017. The attack may be launched remotely. No form of authentication is required for 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 08/03/2020). It is expected to see the exploit prices for this product increasing in the near future.The MITRE ATT&CK project declares the attack technique as T1068.

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†). The entries VDB-96042, VDB-96043, VDB-96045 and VDB-96046 are related to this item. 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: 6.4
VulDB Meta Temp Score: 6.2

VulDB Base Score: 6.3
VulDB Temp Score: 6.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

Name: Address
Class: Access control / Address
CWE: CWE-284 / CWE-266
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/03/2020 +1263 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-5015 (🔍)
GCVE (CVE): GCVE-0-2017-5015
GCVE (VulDB): GCVE-100-96044

OVAL: 🔍

SecurityFocus: 95792 - Google Chrome Multiple Security Vulnerabilities
OSVDB: - CVE-2017-5015 - Google - Chrome - Spoofing Issue
SecurityTracker: 1037718

See also: 🔍

Entryinfo

Created: 01/27/2017 12:22
Updated: 08/03/2020 09:02
Changes: 01/27/2017 12:22 (84), 08/03/2020 09:02 (9)
Complete: 🔍
Cache ID: 216:F17:103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!