| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Google Android and classified as problematic. Affected by this vulnerability is an unknown functionality of the component Qualcomm. This manipulation causes information disclosure. The identification of this vulnerability is CVE-2016-3902. The attack can only be executed locally. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability has been found in Google Android (Smartphone Operating System) (the affected version unknown) and classified as problematic. Affected by this vulnerability is an unknown part of the component Qualcomm. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality.
The weakness was shared 10/05/2016 by Seven Shen with Trend Micro as Android Security Bulletin - October 2016 as confirmed security bulletin (Website). The advisory is shared at source.android.com. This vulnerability is known as CVE-2016-3902 since 03/30/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. 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 93309†). The entries VDB-83735, VDB-90675, VDB-90618 and VDB-90676 are related to this item. 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: 🔍
Patch: source.codeaurora.org
Timeline
03/30/2016 🔍10/03/2016 🔍
10/05/2016 🔍
10/05/2016 🔍
10/05/2016 🔍
10/10/2016 🔍
09/22/2022 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - October 2016
Researcher: Seven Shen
Organization: Trend Micro
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-3902 (🔍)
GCVE (CVE): GCVE-0-2016-3902
GCVE (VulDB): GCVE-100-92389
SecurityFocus: 93309 - Linux Kernel Multiple Information Disclosure Vulnerabilities
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 10/05/2016 10:44Updated: 09/22/2022 10:02
Changes: 10/05/2016 10:44 (54), 05/01/2019 20:22 (15), 09/22/2022 10:02 (4)
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.