VDB-111453 · CVE-2017-14912 · BID 102386

Google Android Qualcomm 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.
9.4	$5k-$25k	0.00

Summaryinfo

A vulnerability classified as critical has been found in Google Android. Affected by this issue is some unknown functionality of the component Qualcomm Component. Performing a manipulation results in memory corruption. This vulnerability was named CVE-2017-14912. The attack may be initiated remotely. There is no available exploit. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in Google Android (Smartphone Operating System) (version now known). It has been classified as very critical. This affects some unknown processing of the component Qualcomm Component. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.

The bug was discovered 01/29/2018. The weakness was presented 01/02/2018 as Android Security Bulletin - January 2018 as confirmed security bulletin (Website). The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2017-14912 since 09/28/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 01/29/2021). It is expected to see the exploit prices for this product increasing in the near future.

Applying a patch is able to eliminate this problem. A possible mitigation has been published 3 days after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at SecurityFocus (BID 102386†) and SecurityTracker (ID 1040106†). See VDB-111420, VDB-111421, VDB-111439 and VDB-111438 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Smartphone Operating System

Vendor

Google

Name

Android

License

free

Website

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

CPE 2.3info

🔍

CPE 2.2info

🔍

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.8
VulDB Meta Temp Score: 9.6

VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.8
NVD Vector: 🔍

CVSSv2info

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

Exploitinginfo

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

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

09/28/2017 🔍
01/02/2018 +96 days 🔍
01/02/2018 +0 days 🔍
01/05/2018 +3 days 🔍
01/05/2018 +0 days 🔍
01/07/2018 +2 days 🔍
01/29/2018 +22 days 🔍
03/30/2018 +60 days 🔍
01/29/2021 +1036 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: Android Security Bulletin - January 2018
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-14912 (🔍)
GCVE (CVE): GCVE-0-2017-14912
GCVE (VulDB): GCVE-100-111453
SecurityFocus: 102386 - Google Android Multiple Qualcomm Components Multiple Unspecified Security Vulnerabilities
SecurityTracker: 1040106

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

Entryinfo

Created: 01/07/2018 11:30
Updated: 01/29/2021 09:10
Changes: 01/07/2018 11:30 (68), 12/20/2019 09:17 (5), 01/29/2021 09:10 (2)
Complete: 🔍
Cache ID: 216::103

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