| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $5k-$25k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Google Android 6.x. The impacted element is an unknown function of the component Framework UI. The manipulation leads to access control. This vulnerability is referenced as CVE-2016-2496. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Google Android 6.x (Smartphone Operating System). It has been rated as critical. This issue affects an unknown code of the component Framework UI. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The Framework UI permission-dialog implementation in Android 6.x before 2016-06-01 allows attackers to conduct tapjacking attacks and access arbitrary private-storage files by creating a partially overlapping window, aka internal bug 26677796.
The weakness was published 06/13/2016 as 26677796 as confirmed advisory (Website). It is possible to read the advisory at android.googlesource.com. The identification of this vulnerability is CVE-2016-2496 since 02/18/2016. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 01/18/2019). 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.
Upgrading to version 6.x 2016-06-01 eliminates this vulnerability.
Similar entries are available at VDB-87840, VDB-87841, VDB-87842 and VDB-87843. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Upgrade: Android 6.x 2016-06-01
Timeline
02/18/2016 🔍06/12/2016 🔍
06/13/2016 🔍
06/13/2016 🔍
01/18/2019 🔍
Sources
Vendor: google.comAdvisory: 26677796
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-2496 (🔍)
GCVE (CVE): GCVE-0-2016-2496
GCVE (VulDB): GCVE-100-87875
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 06/13/2016 10:17Updated: 01/18/2019 08:31
Changes: 06/13/2016 10:17 (61), 01/18/2019 08:31 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.