VDB-95227 · CVE-2016-6768 · BID 94704

Google Android up to 7.0 Framesequence Library access control

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.0$25k-$100k0.00

Summaryinfo

A vulnerability classified as critical has been found in Google Android 5.0.2/5.1.1/6.0/6.0.1/7.0. Affected by this vulnerability is an unknown functionality of the component Framesequence Library. This manipulation causes access control. This vulnerability is tracked as CVE-2016-6768. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Google Android 5.0.2/5.1.1/6.0/6.0.1/7.0 (Smartphone Operating System). It has been declared as critical. Affected by this vulnerability is some unknown processing of the component Framesequence Library. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The bug was discovered 12/05/2016. The weakness was disclosed 01/12/2017 by Marco Grassi with Tencent (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is known as CVE-2016-6768 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 $25k-$100k at the moment (estimation calculated on 07/20/2020). It is expected to see the exploit prices for this product increasing in the near future.The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 38 days. During that time the estimated underground price was around $25k-$100k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 94704†). The entries VDB-90448, VDB-90450, VDB-95213 and VDB-95214 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.0
VulDB Meta Temp Score: 7.0

VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

08/11/2016 🔍
12/05/2016 +116 days 🔍
12/05/2016 +0 days 🔍
01/12/2017 +38 days 🔍
01/12/2017 +0 days 🔍
01/13/2017 +1 days 🔍
07/20/2020 +1284 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: securityfocus.com⛔
Researcher: Marco Grassi
Organization: Tencent
Status: Not defined
Confirmation: 🔍

CVE: CVE-2016-6768 (🔍)
GCVE (CVE): GCVE-0-2016-6768
GCVE (VulDB): GCVE-100-95227
SecurityFocus: 94704 - Google Android Framesequence Library CVE-2016-6768 Remote Code Execution Vulnerability
OSVDB: - CVE-2016-6768 - Google - Android - Medium

scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍

Entryinfo

Created: 01/13/2017 08:08
Updated: 07/20/2020 15:53
Changes: 01/13/2017 08:08 (60), 07/20/2020 15:53 (8)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!