Google Android Qualcomm SPCom Driver Drivers/soc/qcom/spcom.c access control

CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.1 | $5k-$25k | 0.00 |
A vulnerability classified as problematic has been found in Google Android (Smartphone Operating System) (version unknown). This affects an unknown function of the file Drivers/soc/qcom/spcom.c of the component Qualcomm SPCom Driver. 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 confidentiality, integrity, and availability. The summary by CVE is:
Drivers/soc/qcom/spcom.c in the Qualcom SPCom driver in the Android kernel 2017-03-05 allows local users to gain privileges, a different vulnerability than CVE-2016-5857.
The bug was discovered 04/04/2017. The weakness was shared 04/12/2017 (Website). The advisory is shared at securitytracker.com. This vulnerability is uniquely identified as CVE-2016-5856 since 06/28/2016. An attack has to be approached locally. The successful exploitation requires a authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 11/29/2022). It is expected to see the exploit prices for this product increasing in the near future.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 8 days. During that time the estimated underground price was around $5k-$25k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-97625, VDB-97626, VDB-97627 and VDB-97628 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.1VulDB Meta Temp Score: 6.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: source.codeaurora.org
Timeline
06/28/2016 🔍04/04/2017 🔍
04/12/2017 🔍
04/12/2017 🔍
04/13/2017 🔍
11/29/2022 🔍
Sources
Vendor: google.comAdvisory: securitytracker.com⛔
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-5856 (🔍)
GCVE (CVE): GCVE-0-2016-5856
GCVE (VulDB): GCVE-100-99729
OSVDB: - CVE-2016-5856 - Linux - Kernel - Privilege Escalation Issue
SecurityTracker: 1037968
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 04/13/2017 11:56 AMUpdated: 11/29/2022 07:52 AM
Changes: 04/13/2017 11:56 AM (60), 09/29/2020 04:45 PM (2), 11/29/2022 07:52 AM (4)
Complete: 🔍
Cache ID: 18:95D:40
No comments yet. Languages: en.
Please log in to comment.