VDB-88917 · CVE-2014-9799 · BID 91628

Google Android prior 2016-07-05 on Nexus 5/Nexus 7 2013 Qualcomm makefile -fno-strict-overflow access control

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

Summaryinfo

A vulnerability has been found in Google Android on Nexus 5/Nexus 7 2013 and classified as problematic. This issue affects some unknown processing of the file makefile of the component Qualcomm. Performing a manipulation of the argument -fno-strict-overflow results in access control. This vulnerability is reported as CVE-2014-9799. The attack requires a local approach. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Google Android on Nexus 5/Nexus 7 2013 (Smartphone Operating System). It has been classified as critical. This affects an unknown part of the file makefile of the component Qualcomm. The manipulation of the argument -fno-strict-overflow 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:

The makefile in the Qualcomm components in Android before 2016-07-05 on Nexus 5 and 7 (2013) devices omits the -fno-strict-overflow option to gcc, which might allow attackers to gain privileges via a crafted application that leverages incorrect compiler optimization of an integer-overflow protection mechanism, aka Android internal bug 28821731 and Qualcomm internal bug CR691916.

The weakness was disclosed 07/06/2016 as Android Security Bulletin - July 2016 as confirmed security bulletin (Website). The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2014-9799 since 05/31/2016. The exploitability is told to be easy. An attack has to be approached locally. A authentication is necessary for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 2016-07-05 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 91628†). The entries VDB-88897, VDB-88898, VDB-88899 and VDB-88900 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.8
VulDB Meta Temp Score: 7.6

VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

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

Upgrade: Android 2016-07-05
Patch: source.codeaurora.org

Timelineinfo

05/31/2016 🔍
07/06/2016 +36 days 🔍
07/06/2016 +0 days 🔍
07/07/2016 +1 days 🔍
07/10/2016 +3 days 🔍
07/11/2016 +1 days 🔍
09/01/2022 +2243 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: Android Security Bulletin - July 2016
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2014-9799 (🔍)
GCVE (CVE): GCVE-0-2014-9799
GCVE (VulDB): GCVE-100-88917
SecurityFocus: 91628 - Google Nexus Qualcomm Components Multiple Privilege Escalation Vulnerabilities

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

Entryinfo

Created: 07/11/2016 11:00
Updated: 09/01/2022 11:25
Changes: 07/11/2016 11:00 (59), 02/21/2019 13:45 (13), 09/01/2022 11:25 (4)
Complete: 🔍
Cache ID: 216::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 want to use VulDB in your project?

Use the official API to access entries easily!