Google Android 4.3 Key Store KeyStore::getKeyForName memory corruption

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.
6.4$5k-$25k0.00

Summaryinfo

A vulnerability, which was classified as critical, was found in Google Android 4.3. Affected by this issue is the function KeyStore::getKeyForName of the component Key Store. Executing a manipulation can lead to memory corruption. This vulnerability appears as CVE-2014-3100. There is no available exploit. This vulnerability has a historic impact due to its background and reception. You should upgrade the affected component.

Detailsinfo

A vulnerability has been found in Google Android 4.3 (Smartphone Operating System) and classified as critical. This vulnerability affects the function KeyStore::getKeyForName of the component Key Store. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was presented 06/23/2014 by Roee Hay as ANDROID-10676015 as confirmed article (Website). The advisory is shared for download at securityintelligence.com. The public release was coordinated in cooperation with the vendor. This vulnerability was named CVE-2014-3100 since 04/29/2014. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 08/01/2021). It is expected to see the exploit prices for this product increasing in the near future.This vulnerability has a historic impact due to its background and reception.

The vulnerability was handled as a non-public zero-day exploit for at least 63 days. During that time the estimated underground price was around $25k-$100k.

Upgrading to version 4.4 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (93916), SecurityFocus (BID 68152†), SecurityTracker (ID 1030492†) and Vulnerability Center (SBV-47630†). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.4

VulDB Base Score: 7.3
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Unproven

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: 🔍

Upgrade: Android 4.4

Timelineinfo

09/09/2013 🔍
09/09/2013 +0 days 🔍
11/11/2013 +63 days 🔍
04/29/2014 +169 days 🔍
06/23/2014 +55 days 🔍
06/23/2014 +0 days 🔍
06/23/2014 +0 days 🔍
06/30/2014 +7 days 🔍
07/02/2014 +2 days 🔍
12/16/2014 +167 days 🔍
03/17/2015 +91 days 🔍
08/01/2021 +2329 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: ANDROID-10676015
Researcher: Roee Hay
Status: Confirmed
Coordinated: 🔍

CVE: CVE-2014-3100 (🔍)
GCVE (CVE): GCVE-0-2014-3100
GCVE (VulDB): GCVE-100-43528
X-Force: 93916 - Android KeyStore::getKeyForName buffer overflow, High Risk
SecurityFocus: 68152 - Android KeyStore Service CVE-2014-3100 Stack Buffer Overflow Vulnerability
SecurityTracker: 1030492 - Android KeyStore Stack Overflow Lets Applications Obtain Potentially Sensitive Information
Vulnerability Center: 47630 - Android 4.3 KeyStore Service Remote Code Execution Vulnerability via a Long Key Name, High

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

Entryinfo

Created: 03/17/2015 12:19
Updated: 08/01/2021 16:02
Changes: 03/17/2015 12:19 (75), 06/15/2017 11:31 (3), 08/01/2021 16:02 (3)
Complete: 🔍
Cache ID: 216:1B8:103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

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!