Google Android Qualcomm QSEE Communicator Driver access control

CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.6 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Google Android and classified as critical. This issue affects some unknown processing of the component Qualcomm QSEE Communicator Driver. The manipulation leads to access control. The identification of this vulnerability is CVE-2016-3931. Attacking locally is a requirement. There is no exploit available. It is recommended to upgrade the affected component. Once again VulDB remains the best source for vulnerability data.
Details
A vulnerability has been found in Google Android (Smartphone Operating System) (the affected version is unknown) and classified as critical. This vulnerability affects an unknown code of the component Qualcomm QSEE Communicator Driver. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was disclosed 10/05/2016 as Android Security Bulletin - October 2016 as confirmed security bulletin (Website). The advisory is available at source.android.com. This vulnerability was named CVE-2016-3931 since 03/30/2016. Local access is required to approach this attack. A single authentication is needed for exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of 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.This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
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 93313†). The entries VDB-83735, VDB-90675, VDB-90618 and VDB-90676 are pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
License
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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
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: 🔍
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
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-3931 (🔍)
GCVE (CVE): GCVE-0-2016-3931
GCVE (VulDB): GCVE-100-92362
SecurityFocus: 93313 - Linux Kernel CVE-2016-3931 Remote Code Execution Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 10/05/2016 10:44 AMUpdated: 09/22/2022 09:29 AM
Changes: 10/05/2016 10:44 AM (54), 05/01/2019 04:42 PM (13), 09/22/2022 09:29 AM (4)
Complete: 🔍
Cache ID: 18:7F3:40
No comments yet. Languages: en.
Please log in to comment.