Google Android up to 4.4.3/5.0.1/5.1.0/6.x sdcard/sdcard.c access control

Summaryinfo

A vulnerability identified as problematic has been detected in Google Android up to 4.4.3/5.0.1/5.1.0/6.x. Impacted is an unknown function of the file sdcard/sdcard.c. Performing a manipulation results in access control. This vulnerability was named CVE-2016-2494. In addition, an exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Android up to 4.4.3/5.0.1/5.1.0/6.x (Smartphone Operating System). It has been classified as problematic. This affects some unknown functionality of the file sdcard/sdcard.c. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Off-by-one error in sdcard/sdcard.c in Android 4.x before 4.4.4, 5.0.x before 5.0.2, 5.1.x before 5.1.1, and 6.x before 2016-06-01 allows attackers to gain privileges via a crafted application, as demonstrated by obtaining Signature or SignatureOrSystem access, aka internal bug 28085658.

The weakness was presented 06/13/2016 as 28085658 as confirmed advisory (Website). The advisory is shared at android.googlesource.com. This vulnerability is uniquely identified as CVE-2016-2494 since 02/18/2016. An attack has to be approached locally. A authentication is required for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1068 for this issue.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $100k and more.

Upgrading to version 4.4.4, 5.0.2, 5.1.1 or 6.0 2016-06-01 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Exploit-DB (39921). See VDB-87840, VDB-87841, VDB-87842 and VDB-87843 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Smartphone Operating System

Vendor

• Google

Name

• Android

Version

• 1.0
• 1.1
• 1.5
• 1.6
• 2.0
• 2.0.1
• 2.1
• 2.2
• 2.2.1
• 2.2.2
• 2.2.3
• 2.3
• 2.3.1
• 2.3.2
• 2.3.3
• 2.3.4
• 2.3.5
• 2.3.6
• 2.3.7
• 3.0
• 3.1
• 3.2
• 3.2.1
• 3.2.2
• 3.2.3
• 3.2.4
• 3.2.5
• 3.2.6
• 4.0
• 4.0.1
• 4.0.2
• 4.0.3
• 4.0.4
• 4.1
• 4.1.1
• 4.1.2
• 4.2
• 4.2.1
• 4.2.2
• 4.3
• 4.3.1
• 4.4
• 4.4.1
• 4.4.2
• 4.4.3
• 4.4.4
• 5.0
• 5.0.1
• 5.1.0
• 6.x

License

• free

Website

• Vendor: https://www.google.com/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion