Google Android 7.0/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.2$0-$5k0.00

Summaryinfo

A vulnerability was found in Google Android 7.0/7.1.1. It has been classified as problematic. The impacted element is an unknown function of the component Framework API. Performing a manipulation results in access control. This vulnerability is known as CVE-2017-0412. Attacking locally is a requirement. Furthermore, an exploit is available.

Detailsinfo

A vulnerability was found in Google Android 7.0/7.1.1 (Smartphone Operating System). It has been classified as problematic. This affects an unknown code block of the component Framework API. 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 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: 7.0, 7.1.1. Android ID: A-33039926.

The bug was discovered 02/06/2017. The weakness was published 02/08/2017 by Gal Beniamini with Google Security Research (Website). It is possible to read the advisory at source.android.com. This vulnerability is uniquely identified as CVE-2017-0412 since 11/29/2016. Attacking locally is a requirement. The requirement for exploitation is a authentication. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

After 6 days, there has been an exploit disclosed. The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. 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 databases at Exploit-DB (41355) and SecurityFocus (BID 96056†). Similar entries are available at VDB-96659, VDB-96660, VDB-96661 and VDB-96662. 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: 6.3
VulDB Meta Temp Score: 6.2

VulDB Base Score: 4.8
VulDB Temp Score: 4.6
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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍
Exploit Delay 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 🔍
02/14/2017 +6 days 🔍
02/14/2017 +0 days 🔍
06/07/2024 +2670 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: source.android.com
Researcher: Gal Beniamini
Organization: Google Security Research
Status: Confirmed
Confirmation: 🔍

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

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

Entryinfo

Created: 02/08/2017 21:07
Updated: 06/07/2024 15:11
Changes: 02/08/2017 21:07 (74), 08/15/2020 15:13 (1), 11/12/2022 08:43 (3), 06/07/2024 15:11 (15)
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 ▸

Do you know our Splunk app?

Download it now for free!