VDB-91422 · CVE-2016-3876 · BID 92819

Google Android prior 6.0/6.0.1/7.0 Settings 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.6$0-$5k0.00

A vulnerability classified as critical has been found in Google Android (Smartphone Operating System). Affected is some unknown functionality of the component Settings. 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 weakness was disclosed 09/06/2016 as Android Security Bulletin - September 2016 as confirmed security bulletin (Website). The advisory is available at source.android.com. This vulnerability is traded as CVE-2016-3876 since 03/30/2016. The exploitability is told to be easy. Local access is required to approach this attack. A authentication is required for exploitation. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 09/15/2022). It is expected to see the exploit prices for this product increasing in the near future.This vulnerability is assigned to T1068 by the MITRE ATT&CK project.

Upgrading to version 6.0, 6.0.1 or 7.0 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The entries 91415, 91416, 91417 and 91418 are pretty similar.

Productinfo

Type

Vendor

Name

License

  • free

CPE 2.3info

CPE 2.2info

CVSSv3info

VulDB Meta Base Score: 6.8
VulDB Meta Temp Score: 6.6

VulDB Base Score: 6.8
VulDB Temp Score: 6.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.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
ATT&CK: T1068

Local: Yes
Remote: No

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: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Android 6.0/6.0.1/7.0

Timelineinfo

03/30/2016 🔍
09/06/2016 +160 days 🔍
09/06/2016 +0 days 🔍
09/07/2016 +1 days 🔍
09/11/2016 +4 days 🔍
09/11/2016 +0 days 🔍
09/15/2022 +2195 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: Android Security Bulletin - September 2016
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-3876 (🔍)
SecurityTracker: 1036763
SecurityFocus: 92819 - Google Android CVE-2016-3876 Local Privilege Escalation Vulnerability

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

Entryinfo

Created: 09/11/2016 12:29 PM
Updated: 09/15/2022 12:39 PM
Changes: 09/11/2016 12:29 PM (54), 04/14/2019 06:44 AM (12), 09/15/2022 12:39 PM (4)
Complete: 🔍

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!