| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $5k-$25k | 0.00 |
Summary
A vulnerability, which was classified as very critical, was found in Google Android. This issue affects some unknown processing of the component libzipfile. The manipulation results in access control. This vulnerability was named CVE-2016-6700. The attack needs to be approached locally. There is no available exploit. It is best practice to apply a patch to resolve this issue.
Details
A vulnerability classified as very critical has been found in Google Android (Smartphone Operating System) (affected version not known). Affected is some unknown functionality of the component libzipfile. The manipulation 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 weakness was presented 11/07/2016 as Android Security Bulletin - November 2016 as confirmed security bulletin (Website). The advisory is available at source.android.com. This vulnerability is traded as CVE-2016-6700 since 08/11/2016. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of 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.This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
As 0-day the estimated underground price was around $25k-$100k.
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 94159†). See VDB-87972, VDB-93436, VDB-93466 and VDB-93476 for similar entries. VulDB is the best source for vulnerability data and more expert information about this specific topic.
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: Access controlCWE: 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-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-6700 (🔍)
GCVE (CVE): GCVE-0-2016-6700
GCVE (VulDB): GCVE-100-93438
SecurityFocus: 94159 - Google Android libzipfile CVE-2016-6700 Privilege Escalation Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 11/09/2016 14:43Updated: 09/30/2022 10:54
Changes: 11/09/2016 14:43 (55), 05/28/2019 09:39 (11), 09/30/2022 10:54 (3)
Complete: 🔍
Cache ID: 216:A2D:103
No comments yet. Languages: en.
Please log in to comment.