| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $25k-$100k | 0.00 |
Summary
A vulnerability classified as critical has been found in Google Android. This vulnerability affects unknown code of the component HTC Sensor Hub Driver. This manipulation causes access control. This vulnerability is registered as CVE-2017-0526. The attack needs to be launched locally. No exploit is available.
Details
A vulnerability classified as critical was found in Google Android (Smartphone Operating System) (version now known). Affected by this vulnerability is some unknown processing of the component HTC Sensor Hub 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 summary by CVE is:
An elevation of privilege vulnerability in the HTC Sensor Hub Driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process. Product: Android. Versions: Kernel-3.10. Android ID: A-33897738.
The bug was discovered 03/06/2017. The weakness was published 03/08/2017 by Di Shen with Tencent (Website). The advisory is shared at source.android.com. This vulnerability is known as CVE-2017-0526 since 11/29/2016. An attack has to be approached locally. Required for exploitation is a single authentication. 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 1 days. During that time the estimated underground price was around $25k-$100k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 96949†). Similar entries are available at VDB-94929, VDB-94930, VDB-94931 and VDB-94932. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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.4VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.8
VulDB Temp Score: 7.8
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/29/2016 🔍03/06/2017 🔍
03/07/2017 🔍
03/07/2017 🔍
03/08/2017 🔍
03/08/2017 🔍
09/05/2020 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Researcher: Di Shen
Organization: Tencent
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-0526 (🔍)
GCVE (CVE): GCVE-0-2017-0526
GCVE (VulDB): GCVE-100-97705
SecurityFocus: 96949 - Google Android HTC Sensor Hub Driver Multiple Privilege Escalation Vulnerabilities
OSVDB: - CVE-2017-0526 - Linux - Kernel - Privilege Escalation Issue
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 03/08/2017 13:22Updated: 09/05/2020 14:08
Changes: 03/08/2017 13:22 (61), 09/05/2020 14:08 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.