VDB-8005 · OSVDB 91282 · GCVE-100-8005

Google Android 4.1 MOUNT_FORMAT_FILESYSTEMS 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.
3.0$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Google Android 4.1. This affects the function MOUNT_FORMAT_FILESYSTEMS. This manipulation causes information disclosure. Furthermore, an exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Google Android 4.1 (Smartphone Operating System) and classified as problematic. Affected by this vulnerability is the function MOUNT_FORMAT_FILESYSTEMS. The manipulation with an unknown input 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.

The weakness was published 03/14/2013 by Jann Horn as not defined mailinglist post (Full-Disclosure). The advisory is shared at seclists.org. The public release happened without involvement of Google. Technical details and also a private exploit are known. MITRE ATT&CK project uses the attack technique T1592 for this issue.

It is declared as proof-of-concept.

Upgrading to version 4.2 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at OSVDB (91282†). Similar entries are available at VDB-7999, VDB-8008, VDB-8000 and VDB-8001. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.0

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

CVSSv2info

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

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

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Private
Status: Proof-of-Concept
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Android 4.2

Timelineinfo

03/14/2013 🔍
03/18/2013 +4 days 🔍
05/04/2018 +1873 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: seclists.org
Researcher: Jann Horn
Status: Not defined

GCVE (VulDB): GCVE-100-8005
OSVDB: 91282

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

Entryinfo

Created: 03/18/2013 08:04
Updated: 05/04/2018 09:10
Changes: 03/18/2013 08:04 (46), 05/04/2018 09:10 (2)
Complete: 🔍
Committer:
Cache ID: 216:AA6:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!