| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Google Android and classified as problematic. Affected by this issue is some unknown functionality of the component Qualcomm Codec. Performing a manipulation results in access control. This vulnerability is identified as CVE-2016-5862. The attack is only possible with local access. There is not any exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability classified as problematic has been found in Google Android (Smartphone Operating System) (the affected version unknown). This affects an unknown part of the component Qualcomm Codec. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on availability. The summary by CVE is:
When a control related to codec is issued from userspace in all Qualcomm products with Android release from CAF using the Linux kernel, the type casting is done to the container structure instead of the codec's individual structure, resulting in a device restart after kernel crash occurs.
The bug was discovered 05/05/2017. The weakness was released 08/16/2017 (Website). The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2016-5862 since 06/28/2016. An attack has to be approached locally. A authentication is necessary for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 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 98194†). Entries connected to this vulnerability are available at VDB-100815, VDB-101104, VDB-101105 and VDB-101106. 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.1VulDB Meta Temp Score: 5.1
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.0
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: 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/28/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-5862 (🔍)
GCVE (CVE): GCVE-0-2016-5862
GCVE (VulDB): GCVE-100-105381
SecurityFocus: 98194 - Google Android Qualcomm Sound Codec Driver CVE-2016-5862 Privilege Escalation Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 08/16/2017 22:04Updated: 12/15/2022 20:06
Changes: 08/16/2017 22:04 (62), 11/07/2019 15:16 (4), 12/15/2022 20:06 (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.