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

CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.6 | $5k-$25k | 0.00 |
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. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/01/2022). It is expected to see the exploit prices for this product increasing in the near future.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. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 0.c
- 1.0
- 1.1
- 1.5
- 1.6
- 1.c
- 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
- 2.37
- 2.c
- 2.java
- 3.0
- 3.1
- 3.2
- 3.2.1
- 3.2.2
- 3.2.3
- 3.2.4
- 3.2.5
- 3.2.6
- 3.8
- 3.10
- 3.15-rc5-next-20140519
- 3.18
- 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.1_r1
- 4.4.2
- 4.4.3
- 4.4.4
- 4.9
- 4.14 LTS
- 4.cpp
- 5
- 5.0
- 5.0.1
- 5.0.2
- 5.1
- 5.1.0
- 5.1.1
- 5.1.1 LMY48X
- 5.1.1 LMY48Z
- 5.1.1 LMY49F
- 5.2
- 6
- 6.0
- 6.0 2015-10-01
- 6.0 2015-10-01
- 6.0 2015-11-01
- 6.0 2015-12-01
- 6.0 2015-1201
- 6.0 2016-01-01
- 6.0 2016-06-01
- 6.0 2016-07-01
- 6.0 Security Patch Level 11-01-2015
- 6.0.1
- 6.1
- 6.cpp
- 6.x 2016-06-01
- 6.x 2016-07-01
- 6.x 2016-07-05
- 7
- 7.0
- 7.1
- 7.1.1
- 7.1.2
- 8
- 8.0
- 8.1
- 8.1.0
- 9
- 9.0
- 10
- 10.0
- 11
- 11.0
- 12
- 12.0
- 12L
- 13
- 13.0
- 14
- 15
- 18.0.1
- 101.c
- 1012
- 2013-01-16
- 2013-07-07
- 2016-06-01
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB 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: 🔍
CVSSv2
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: 🔍
Exploiting
Class: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Local: Yes
Remote: No
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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Android 2016-07-05
Patch: source.codeaurora.org
Timeline
05/31/2016 🔍07/06/2016 🔍
07/06/2016 🔍
07/07/2016 🔍
07/10/2016 🔍
07/11/2016 🔍
09/01/2022 🔍
Sources
Vendor: google.comAdvisory: 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: 🔍
Entry
Created: 07/11/2016 11:00 AMUpdated: 09/01/2022 11:25 AM
Changes: 07/11/2016 11:00 AM (59), 02/21/2019 01:45 PM (13), 09/01/2022 11:25 AM (4)
Complete: 🔍
Cache ID: 18:124:40
No comments yet. Languages: en.
Please log in to comment.