VDB-96673 · CVE-2017-0410 · BID 96056

Google Android up to 7.1.1 Framework API 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.
6.3$5k-$25k0.00

Summaryinfo

A vulnerability has been found in Google Android up to 7.1.1 and classified as problematic. Impacted is an unknown function of the component Framework API. This manipulation causes access control. This vulnerability appears as CVE-2017-0410. The attack requires local access. There is no available exploit.

Detailsinfo

A vulnerability has been found in Google Android up to 7.1.1 (Smartphone Operating System) and classified as problematic. Affected by this vulnerability is an unknown part of the component Framework API. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

An elevation of privilege vulnerability in the Framework APIs could enable a local malicious application to execute arbitrary code within the context of a privileged process. This issue is rated as High because it could be used to gain local access to elevated capabilities, which are not normally accessible to a third-party application. Product: Android. Versions: 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1. Android ID: A-31929765.

The bug was discovered 02/06/2017. The weakness was presented 02/08/2017 by Gal Beniamini (Website). The advisory is shared at source.android.com. This vulnerability is known as CVE-2017-0410 since 11/29/2016. An attack has to be approached locally. A single authentication is necessary for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 11/12/2022). It is expected to see the exploit prices for this product increasing in the near future.MITRE ATT&CK project uses the attack technique T1068 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 2 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 96056†). See VDB-96659, VDB-96660, VDB-96661 and VDB-96662 for similar entries. Several companies clearly confirm that VulDB is the primary source for best 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: 6.3
VulDB Meta Temp Score: 6.3

VulDB Base Score: 4.8
VulDB Temp Score: 4.8
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-264
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

11/29/2016 🔍
02/06/2017 +69 days 🔍
02/06/2017 +0 days 🔍
02/08/2017 +2 days 🔍
02/08/2017 +0 days 🔍
02/08/2017 +0 days 🔍
11/12/2022 +2103 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: source.android.com
Researcher: Gal Beniamini
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-0410 (🔍)
GCVE (CVE): GCVE-0-2017-0410
GCVE (VulDB): GCVE-100-96673
SecurityFocus: 96056 - Google Android Framework APIs Multiple Privilege Escalation Vulnerabilities
OSVDB: - CVE-2017-0410 - Google - Android - High
SecurityTracker: 1037798

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

Entryinfo

Created: 02/08/2017 21:07
Updated: 11/12/2022 08:39
Changes: 02/08/2017 21:07 (61), 08/13/2020 22:07 (7), 11/12/2022 08:39 (2)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!