| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $5k-$25k | 0.77 |
Summary
A vulnerability identified as critical has been detected in Google Android. This vulnerability affects unknown code of the component Qualcomm Wi-Fi Driver. The manipulation leads to memory corruption. This vulnerability is documented as CVE-2016-5342. The attack needs to be performed locally. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (affected version not known) and classified as critical. This issue affects some unknown functionality of the component Qualcomm Wi-Fi Driver. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability.
The weakness was released 10/05/2016 as Android Security Bulletin - October 2016 as confirmed security bulletin (Website). The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2016-5342 since 06/09/2016. An attack has to be approached locally. A simple authentication is required for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/22/2022). It is expected to see the exploit prices for this product increasing in the near future.
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 92693†). Entries connected to this vulnerability are available at VDB-83735, VDB-90675, VDB-90618 and VDB-90676. 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: 7.8VulDB Meta Temp Score: 7.6
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: 🔍
Exposure Time: 🔍
Patch: source.codeaurora.org
Timeline
06/09/2016 🔍08/30/2016 🔍
08/30/2016 🔍
10/05/2016 🔍
10/05/2016 🔍
10/05/2016 🔍
09/22/2022 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - October 2016
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-5342 (🔍)
GCVE (CVE): GCVE-0-2016-5342
GCVE (VulDB): GCVE-100-92381
SecurityFocus: 92693 - Linux Kernel CVE-2016-5342 Local Heap Buffer Overflow Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 10/05/2016 10:44Updated: 09/22/2022 09:55
Changes: 10/05/2016 10:44 (54), 05/01/2019 18:19 (13), 09/22/2022 09:55 (5)
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.