| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Google Android. This affects an unknown function of the component NVIDIA Profiler. Performing a manipulation results in information disclosure. This vulnerability is reported as CVE-2016-6686. The attack requires a local approach. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Google Android (Smartphone Operating System) (the affected version is unknown). This affects an unknown code of the component NVIDIA Profiler. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
The NVIDIA profiler in Android before 2016-10-05 on Nexus 9 devices allows attackers to obtain sensitive information via a crafted application, aka internal bug 30163101.
The weakness was disclosed 10/05/2016 as Android Security Bulletin - October 2016 as confirmed security bulletin (Website). The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2016-6686 since 08/11/2016. An attack has to be approached locally. A authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 93324†). The entries VDB-83735, VDB-90675, VDB-90618 and VDB-90676 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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: Information disclosureCWE: CWE-200 / 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
08/11/2016 🔍10/03/2016 🔍
10/05/2016 🔍
10/05/2016 🔍
10/05/2016 🔍
10/10/2016 🔍
05/01/2019 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - October 2016
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-6686 (🔍)
GCVE (CVE): GCVE-0-2016-6686
GCVE (VulDB): GCVE-100-92397
SecurityFocus: 93324 - Google Android NVIDIA Profiler Multiple Information Disclosure Vulnerabilites
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 10/05/2016 10:44Updated: 05/01/2019 21:02
Changes: 10/05/2016 10:44 (56), 05/01/2019 21:02 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.