| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $5k-$25k | 0.00 |
Summary
A vulnerability has been found in Google Android and classified as critical. Impacted is an unknown function of the component Skia. This manipulation causes memory corruption. The identification of this vulnerability is CVE-2016-6701. The attack can only be executed locally. There is no exploit available. It is recommended to apply a patch to fix this issue.
Details
A vulnerability classified as critical was found in Google Android (Smartphone Operating System) (the affected version unknown). Affected by this vulnerability is an unknown part of the component Skia. 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 weakness was shared 11/07/2016 as Android Security Bulletin - November 2016 as confirmed security bulletin (Website). It is possible to read the advisory at source.android.com. This vulnerability is known as CVE-2016-6701 since 08/11/2016. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/30/2022). 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 immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 94162†). The entries VDB-87972, VDB-93436, VDB-93466 and VDB-93476 are related to this item. 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: Memory corruptionCWE: CWE-119
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: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
08/11/2016 🔍11/07/2016 🔍
11/07/2016 🔍
11/07/2016 🔍
11/09/2016 🔍
11/25/2016 🔍
09/30/2022 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - November 2016
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-6701 (🔍)
GCVE (CVE): GCVE-0-2016-6701
GCVE (VulDB): GCVE-100-93439
SecurityFocus: 94162 - Google Android Skia CVE-2016-6701 Memory Corruption Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 11/09/2016 14:43Updated: 09/30/2022 10:59
Changes: 11/09/2016 14:43 (55), 05/28/2019 09:47 (11), 09/30/2022 10:59 (3)
Complete: 🔍
Cache ID: 216:B50:103
No comments yet. Languages: en.
Please log in to comment.