Google Chrome up to 59 on Android Autofill HTML Page information disclosure

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

Summaryinfo

A vulnerability categorized as problematic has been discovered in Google Chrome up to 59 on Android. The impacted element is an unknown function of the component Autofill. Executing a manipulation as part of HTML Page can lead to information disclosure. This vulnerability is handled as CVE-2017-5082. It is possible to launch the attack on the local host. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in Google Chrome up to 59 on Android (Web Browser). This vulnerability affects an unknown functionality of the component Autofill. The manipulation as part of a HTML Page leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. CVE summarizes:

Failure to take advantage of available mitigations in credit card autofill in Google Chrome prior to 59.0.3071.92 for Android allowed a local attacker to take screen shots of credit card information via a crafted HTML page.

The bug was discovered 06/05/2017. The weakness was released 10/27/2017 by Andrey Kovalev with Qihoo 360 Vulcan Team (Website). The advisory is shared for download at security.gentoo.org. This vulnerability was named CVE-2017-5082 since 01/02/2017. The exploitation appears to be easy. The attack needs to be approached locally. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.

The vulnerability was handled as a non-public zero-day exploit for at least 24 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 101124 (Fedora 25 : 1:chromium-native_client (2017-a66e2c5b62)), 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 236369 (Red Hat Update for chromium-browser (RHSA-2017:1399)).

Upgrading to version 59.0.3071.92 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 (101124) and SecurityFocus (BID 98861†). Entries connected to this vulnerability are available at VDB-108663, VDB-108664, VDB-108665 and VDB-108666. 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: 4.4
VulDB Meta Temp Score: 4.3

VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
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

Nessus ID: 101124
Nessus Name: Fedora 25 : 1:chromium-native_client (2017-a66e2c5b62)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 867773
OpenVAS Name: Fedora Update for chromium-native_client FEDORA-2017-b8d76bef4e
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 59.0.3071.92

Timelineinfo

01/02/2017 🔍
06/05/2017 +154 days 🔍
06/05/2017 +0 days 🔍
06/29/2017 +24 days 🔍
06/30/2017 +1 days 🔍
10/27/2017 +119 days 🔍
10/27/2017 +0 days 🔍
10/27/2017 +0 days 🔍
01/04/2023 +1895 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: FEDORA-2017-a66e2c5b62
Researcher: Andrey Kovalev
Organization: Qihoo 360 Vulcan Team
Status: Not defined

CVE: CVE-2017-5082 (🔍)
GCVE (CVE): GCVE-0-2017-5082
GCVE (VulDB): GCVE-100-108676

OVAL: 🔍

SecurityFocus: 98861 - Google Chrome Prior to 59.0.3071.86 Multiple Security Vulnerabilities
SecurityTracker: 1038622

scip Labs: https://www.scip.ch/en/?labs.20130704
See also: 🔍

Entryinfo

Created: 10/27/2017 19:51
Updated: 01/04/2023 19:17
Changes: 10/27/2017 19:51 (84), 12/01/2019 09:04 (2), 01/20/2021 21:03 (2), 01/04/2023 19:09 (3), 01/04/2023 19:17 (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 know our Splunk app?

Download it now for free!