| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Google Android. This impacts an unknown function of the component Qualcomm Sound Codec. The manipulation leads to information disclosure. This vulnerability is listed as CVE-2016-3893. The attack must be carried out locally. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (affected version unknown) and classified as problematic. This issue affects an unknown functionality of the component Qualcomm Sound Codec. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality, integrity, and availability.
The weakness was presented 09/06/2016 as Android Security Bulletin - September 2016 as confirmed security bulletin (Website). It is possible to read the advisory at source.android.com. The identification of this vulnerability is CVE-2016-3893 since 03/30/2016. The exploitation is known to be difficult. Attacking locally is a requirement. The successful exploitation needs a simple authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
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 92884†). See VDB-91415, VDB-91416, VDB-91417 and VDB-91418 for similar entries. 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 🔍09/06/2016 🔍
09/06/2016 🔍
09/06/2016 🔍
09/11/2016 🔍
09/11/2016 🔍
09/15/2022 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - September 2016
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-3893 (🔍)
GCVE (CVE): GCVE-0-2016-3893
GCVE (VulDB): GCVE-100-91463
SecurityFocus: 92884 - Linux Kernel CVE-2016-3893 Information Disclosure Vulnerability
SecurityTracker: 1036763
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 09/11/2016 12:29Updated: 09/15/2022 16:05
Changes: 09/11/2016 12:29 (53), 04/14/2019 10:51 (12), 09/15/2022 16:05 (6)
Complete: 🔍
Cache ID: 216:48F:103
No comments yet. Languages: en.
Please log in to comment.