Google Chrome 18.0.1025306 on Android file URL 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.
4.8$0-$5k0.00

Summaryinfo

A vulnerability was found in Google Chrome 18.0.1025306 on Android. It has been rated as problematic. This issue affects some unknown processing of the component file URL Handler. This manipulation causes access control. This vulnerability is tracked as CVE-2012-4903. Moreover, an exploit is present. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Google Chrome 18.0.1025306 on Android (Web Browser). It has been declared as problematic. Affected by this vulnerability is an unknown function of the component file URL Handler. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality. The summary by CVE is:

Google Chrome before 18.0.1025308 on Android does not properly restrict access to file: URLs, which allows remote attackers to obtain sensitive information via unspecified vectors, as demonstrated by obtaining credential data, a different vulnerability than CVE-2012-4906.

The weakness was disclosed 09/12/2012 by Artem Chaykin as not defined changelog entry (Website). It is possible to read the advisory at googlechromereleases.blogspot.com. The public release has been coordinated in cooperation with Google. This vulnerability is known as CVE-2012-4903 since 09/13/2012. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

It is possible to download the exploit at securityfocus.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k.

Upgrading to version 18.0.1025308 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (78564), SecurityFocus (BID 55523†), OSVDB (85435†), Secunia (SA50613†) and Vulnerability Center (SBV-37089†). The entries VDB-6303, VDB-6304, VDB-6305 and VDB-6306 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality 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: 5.3
VulDB Meta Temp Score: 4.8

VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

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: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Upgrade: Chrome 18.0.1025308

Timelineinfo

09/12/2012 🔍
09/12/2012 +0 days 🔍
09/12/2012 +0 days 🔍
09/12/2012 +0 days 🔍
09/13/2012 +1 days 🔍
09/13/2012 +0 days 🔍
09/14/2012 +1 days 🔍
09/19/2012 +5 days 🔍
11/08/2012 +50 days 🔍
04/20/2017 +1624 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: googlechromereleases.blogspot.com
Researcher: Artem Chaykin
Status: Not defined
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2012-4903 (🔍)
GCVE (CVE): GCVE-0-2012-4903
GCVE (VulDB): GCVE-100-6307
X-Force: 78564
SecurityFocus: 55523 - Google Chrome for Android Prior to 18.0.1025308 Multiple Security Vulnerabilities
Secunia: 50613 - Google Chrome for Android Multiple Vulnerabilities, Moderately Critical
OSVDB: 85435
Vulnerability Center: 37089 - Google Chrome Before 18.0.1025308 on Android Remote Information Disclosure Vulnerability, Medium

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

Entryinfo

Created: 09/19/2012 13:46
Updated: 04/20/2017 14:24
Changes: 09/19/2012 13:46 (76), 04/20/2017 14:24 (3)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!