Google Android Qualcomm Audio Driver Kernel information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Google Android. This issue affects some unknown processing of the component Qualcomm Audio Driver. This manipulation causes information disclosure (Kernel). This vulnerability appears as CVE-2016-5347. The attack requires local access. There is no available exploit. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability classified as problematic was found in Google Android (Smartphone Operating System) (affected version not known). Affected by this vulnerability is some unknown functionality of the component Qualcomm Audio Driver. The manipulation with an unknown input leads to a information disclosure vulnerability (Kernel). 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 summary by CVE is:
In all Qualcomm products with Android releases from CAF using the Linux kernel, kernel stack data can be leaked to userspace by an audio driver.
The bug was discovered 05/05/2017. The weakness was presented 08/16/2017 (Website). The advisory is shared at source.android.com. This vulnerability is known as CVE-2016-5347 since 06/09/2016. An attack has to be approached locally. A single authentication is required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 103 days. During that time the estimated underground price was around $5k-$25k.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 98218†). See VDB-100815, VDB-101104, VDB-101105 and VDB-101106 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: 4.0VulDB Meta Temp Score: 3.9
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.7
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
Name: KernelClass: Information disclosure / Kernel
CWE: 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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: source.codeaurora.org
Timeline
06/09/2016 🔍05/01/2017 🔍
05/05/2017 🔍
08/16/2017 🔍
08/16/2017 🔍
08/16/2017 🔍
12/15/2022 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-5347 (🔍)
GCVE (CVE): GCVE-0-2016-5347
GCVE (VulDB): GCVE-100-105373
SecurityFocus: 98218 - Google Android Qualcomm Sound Driver CVE-2016-5347 Information Disclosure Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 08/16/2017 22:02Updated: 12/15/2022 19:07
Changes: 08/16/2017 22:02 (63), 11/07/2019 14:15 (4), 12/15/2022 19:07 (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.