CVE-2016-6700

Description

An elevation of privilege vulnerability in libzipfile in Android 4.x before 4.4.4, 5.0.x before 5.0.2, and 5.1.x before 5.1.1 could enable a local malicious application to execute arbitrary code within the context of a privileged process. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device. Android ID: A-30916186.

Category

7.8
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.22%
Vendor Advisory android.com
Affected: Google Inc. Android
Published at:
Updated at:

References

Link Tags
https://source.android.com/security/bulletin/2016-11-01.html vendor advisory
http://www.securityfocus.com/bid/94159 third party advisory vdb entry

Frequently Asked Questions

What is the severity of CVE-2016-6700?
CVE-2016-6700 has been scored as a high severity vulnerability.
How to fix CVE-2016-6700?
To fix CVE-2016-6700, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2016-6700 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2016-6700 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2016-6700?
CVE-2016-6700 affects Google Inc. Android.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.