| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android 4.0.3. It has been classified as problematic. Affected by this vulnerability is an unknown functionality. The manipulation leads to input validation. This vulnerability is listed as CVE-2012-6301. There is no available exploit.
Details
A vulnerability, which was classified as problematic, has been found in Google Android 4.0.3 (Smartphone Operating System). This issue affects an unknown code block. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is availability. The summary by CVE is:
The Browser application in Android 4.0.3 allows remote attackers to cause a denial of service (application crash) via a crafted market: URI in the SRC attribute of an IFRAME element.
The weakness was presented 12/10/2012 as File 118539/And (Packetstorm). The advisory is shared at packetstormsecurity.org. The identification of this vulnerability is CVE-2012-6301 since 12/06/2012. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
It is declared as highly functional. We expect the 0-day to have been worth approximately $25k-$100k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (80444) and Vulnerability Center (SBV-47706†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Highly functional
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
MetaSploit ID: android_stock_browser_iframe_dos_cve_2012_6301.rb
MetaSploit Name: Android Stock Browser Iframe DOS
MetaSploit File: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/01/2012 🔍12/06/2012 🔍
12/10/2012 🔍
12/10/2012 🔍
12/21/2014 🔍
03/24/2015 🔍
06/16/2017 🔍
Sources
Vendor: google.comAdvisory: File 118539/And
Status: Confirmed
CVE: CVE-2012-6301 (🔍)
GCVE (CVE): GCVE-0-2012-6301
GCVE (VulDB): GCVE-100-63173
X-Force: 80444
Vulnerability Center: 47706 - Google Android 4.0.3 Browser Application Remote DoS Vulnerability via a Crafted \x27market:\x27 URI, Medium
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 03/24/2015 12:22Updated: 06/16/2017 04:12
Changes: 03/24/2015 12:22 (54), 06/16/2017 04:12 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.