CVE-2016-6768

Name: CVE-2016-6768
Creator: NVD / NIST
Published: 2017-01-12T15:59:00.573+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 0.81%

Last modified Jun 17, 2026

CVE-2016-6768 is a vulnerability of currently unknown severity. A remote code execution vulnerability in the Framesequence library could enable an attacker using a specially crafted file to execute arbitrary code in the context of an unprivileged process. This issue is rated as High due to the possibility of remote code execution in an application that uses the Framesequence library. EPSS estimates a 0.81% chance of exploitation in the next 30 days.

Description

A remote code execution vulnerability in the Framesequence library could enable an attacker using a specially crafted file to execute arbitrary code in the context of an unprivileged process. This issue is rated as High due to the possibility of remote code execution in an application that uses the Framesequence library. Product: Android. Versions: 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0. Android ID: A-31631842.

Metrics

EPSS Probability

0.81%

52.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-284

Affected Software

Vendor	Product	Versions
Google	Android	5.0
Google	Android	5.0.1
Google	Android	5.0.2
Google	Android	5.1
Google	Android	5.1.0
Google	Android	5.1.1
Google	Android	6.0
Google	Android	6.0.1
Google	Android	7.0

References

http://www.securityfocus.com/bid/94704Third Party Advisory, VDB Entry
https://source.android.com/security/bulletin/2016-12-01.htmlVendor Advisory
http://www.securityfocus.com/bid/94704Third Party Advisory, VDB Entry
https://source.android.com/security/bulletin/2016-12-01.htmlVendor Advisory

Timeline

Published: Jan 12, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2016-6768?

How severe is CVE-2016-6768?

Severity scoring for CVE-2016-6768 is pending analysis. The EPSS model estimates a 0.81% probability of exploitation in the next 30 days.

How do I fix CVE-2016-6768?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-6768?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST