Google Android Qualcomm Touch Controller Variable access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Google Android. The affected element is an unknown function of the component Qualcomm Touch Controller. Such manipulation as part of Variable leads to access control. This vulnerability is documented as CVE-2017-6421. The attack needs to be performed locally. There is not any exploit available. A patch should be applied to remediate this issue.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (affected version unknown) and classified as critical. Affected by this issue is an unknown functionality of the component Qualcomm Touch Controller. The manipulation as part of a Variable leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In the touch controller function in all Qualcomm products in all Android releases from CAF using the Linux kernel, a variable may be controlled by the user and can lead to a buffer overflow.
The bug was discovered 06/05/2017. The weakness was released 08/16/2017 (Website). The advisory is available at source.android.com. This vulnerability is handled as CVE-2017-6421 since 03/01/2017. Local access is required to approach this attack. The successful exploitation needs a simple authentication. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 72 days. During that time the estimated underground price was around $5k-$25k.
Applying a patch is able to eliminate this problem.
Entries connected to this vulnerability are available at VDB-102302, VDB-102303, VDB-102304 and VDB-102305. If you want to get best quality of vulnerability data, you may have to visit 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.1VulDB Meta Temp Score: 6.9
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: 🔍
Physical: Partially
Local: Yes
Remote: Partially
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
03/01/2017 🔍06/05/2017 🔍
08/16/2017 🔍
08/16/2017 🔍
08/16/2017 🔍
12/16/2022 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-6421 (🔍)
GCVE (CVE): GCVE-0-2017-6421
GCVE (VulDB): GCVE-100-105386
SecurityTracker: 1038623
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 08/16/2017 22:05Updated: 12/16/2022 06:31
Changes: 08/16/2017 22:05 (60), 11/07/2019 15:35 (2), 01/09/2021 13:34 (3), 12/16/2022 06:31 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.