| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Android. The impacted element is an unknown function of the component TrustZone Syscall Handler. This manipulation causes memory corruption. This vulnerability is handled as CVE-2015-9071. The attack can be initiated remotely. There is not any exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (affected version not known). It has been declared as critical. Affected by this vulnerability is some unknown functionality of the component TrustZone Syscall Handler. 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 summary by CVE is:
In all Qualcomm products with Android releases from CAF using the Linux kernel, a buffer over-read vulnerability exists in a TrustZone syscall.
The bug was discovered 07/01/2017. The weakness was released 08/18/2017 (Website). The advisory is shared at source.android.com. This vulnerability is known as CVE-2015-9071 since 05/30/2017. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. 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 11/08/2019). It is expected to see the exploit prices for this product increasing in the near future.
The vulnerability was handled as a non-public zero-day exploit for at least 48 days. During that time the estimated underground price was around $25k-$100k.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 99467†). Entries connected to this vulnerability are available at VDB-101214, VDB-103224, VDB-103225 and VDB-103226. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.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: Memory corruptionCWE: 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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
05/30/2017 🔍07/01/2017 🔍
07/07/2017 🔍
08/18/2017 🔍
08/18/2017 🔍
08/19/2017 🔍
11/08/2019 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2015-9071 (🔍)
GCVE (CVE): GCVE-0-2015-9071
GCVE (VulDB): GCVE-100-105541
SecurityFocus: 99467 - Qualcomm Closed-Source Components Multiple Unspecified Vulnerabilities
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 08/19/2017 08:47Updated: 11/08/2019 18:06
Changes: 08/19/2017 08:47 (61), 11/08/2019 18:06 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.