Google Android prior 2016-07-05/3.15-rc5-next-20140519 on Nexus 5X/Nexus 6P Linux Kernel 3.15-rc5 pgtable.h data processing
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android on Nexus 5X/Nexus 6P. It has been rated as problematic. This affects an unknown function of the file arch/arm64/include/asm/pgtable.h of the component Linux Kernel 3.15-rc5. This manipulation causes data processing. This vulnerability is handled as CVE-2014-9803. It is possible to launch the attack on the local host. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability classified as critical was found in Google Android on Nexus 5X/Nexus 6P (Smartphone Operating System). Affected by this vulnerability is an unknown function of the file arch/arm64/include/asm/pgtable.h of the component Linux Kernel 3.15-rc5. The manipulation with an unknown input leads to a data processing vulnerability. The CWE definition for the vulnerability is CWE-19. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
arch/arm64/include/asm/pgtable.h in the Linux kernel before 3.15-rc5-next-20140519, as used in Android before 2016-07-05 on Nexus 5X and 6P devices, mishandles execute-only pages, which allows attackers to gain privileges via a crafted application, aka Android internal bug 28557020.
The weakness was released 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 known as CVE-2014-9803 since 06/01/2016. The exploitation appears to be easy. An attack has to be approached locally. The successful exploitation requires a single authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
Upgrading to version 2016-07-05 or 3.15-rc5-next-20140519 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
Entries connected to this vulnerability are available at VDB-88897, VDB-88898, VDB-88899 and VDB-88900. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
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: Data processingCWE: CWE-19
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Android 2016-07-05/3.15-rc5-next-20140519
Patch: git.kernel.org
Timeline
06/01/2016 🔍07/06/2016 🔍
07/06/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-9803 (🔍)
GCVE (CVE): GCVE-0-2014-9803
GCVE (VulDB): GCVE-100-88921
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 07/11/2016 11:01Updated: 09/01/2022 11:53
Changes: 07/11/2016 11:01 (56), 02/21/2019 14:02 (10), 09/01/2022 11:53 (4)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.