Google Chrome 18.0.1025306 on Android API Javascript access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Chrome 18.0.1025306 on Android. It has been classified as problematic. This affects an unknown part of the component API Javascript Handler. The manipulation leads to access control. This vulnerability is referenced as CVE-2012-4907. Furthermore, an exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Google Chrome 18.0.1025306 on Android (Web Browser) and classified as problematic. This issue affects an unknown code block of the component API Javascript Handler. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality. The summary by CVE is:
Google Chrome before 18.0.1025308 on Android does not properly restrict access from JavaScript code to Android APIs, which allows remote attackers to have an unspecified impact via a crafted web page.
The weakness was published 09/12/2012 by Takeshi Terada as not defined changelog entry (Website). The advisory is shared at googlechromereleases.blogspot.com. The public release has been coordinated with Google. The identification of this vulnerability is CVE-2012-4907 since 09/13/2012. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
After 5 months, there has been an exploit disclosed. The exploit is available 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 (78792), SecurityFocus (BID 55523†), OSVDB (85433†), Secunia (SA50613†) and Vulnerability Center (SBV-36438†). code.google.com is providing further details. Similar entries are available at VDB-6303, VDB-6304, VDB-6306 and VDB-6307. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
- Product: https://www.google.com/chrome/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Exploit Delay Time: 🔍
Upgrade: Chrome 18.0.1025308
Timeline
09/12/2012 🔍09/12/2012 🔍
09/12/2012 🔍
09/12/2012 🔍
09/13/2012 🔍
09/13/2012 🔍
09/13/2012 🔍
09/14/2012 🔍
09/19/2012 🔍
10/10/2012 🔍
01/07/2013 🔍
04/17/2017 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: googlechromereleases.blogspot.com
Researcher: Takeshi Terada
Status: Not defined
Confirmation: 🔍
Coordinated: 🔍
CVE: CVE-2012-4907 (🔍)
GCVE (CVE): GCVE-0-2012-4907
GCVE (VulDB): GCVE-100-6305
X-Force: 78792
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: 85433
Vulnerability Center: 36438 - Google Chrome \x3C 18.0.1025308 on Android Improper JavaScript Code Access Restriction, Critical
scip Labs: https://www.scip.ch/en/?labs.20130704
Misc.: 🔍
See also: 🔍
Entry
Created: 09/19/2012 13:45Updated: 04/17/2017 19:51
Changes: 09/19/2012 13:45 (73), 04/17/2017 19:51 (10)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.