| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Google Android. This vulnerability affects unknown code of the component MTK. Performing a manipulation results in access control. This vulnerability is known as CVE-2017-13226. Attacking locally is a requirement. No exploit is available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability, which was classified as critical, was found in Google Android (Smartphone Operating System) (the affected version is unknown). This affects an unknown code of the component MTK. 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:
An elevation of privilege vulnerability in the MediaTek mtk. Product: Android. Versions: Android kernel. Android ID: A-32591194. References: M-ALPS03149184.
The bug was discovered 01/15/2018. The weakness was published 01/02/2018 as Pixel?/?Nexus Security Bulletin - January 2018 as confirmed security bulletin (Website). It is possible to read the advisory at source.android.com. This vulnerability is uniquely identified as CVE-2017-13226 since 08/23/2017. The exploitability is told to be easy. Attacking locally is a requirement. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
Similar entries are available at VDB-111636, VDB-111637, VDB-111638 and VDB-111639. Statistical analysis made it clear that VulDB provides the best quality for 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: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: 🔍
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: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
08/23/2017 🔍01/02/2018 🔍
01/02/2018 🔍
01/11/2018 🔍
01/12/2018 🔍
01/15/2018 🔍
12/21/2019 🔍
Sources
Vendor: google.comAdvisory: Pixel?/?Nexus Security Bulletin - January 2018
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2017-13226 (🔍)
GCVE (CVE): GCVE-0-2017-13226
GCVE (VulDB): GCVE-100-111675
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 01/11/2018 10:26Updated: 12/21/2019 19:06
Changes: 01/11/2018 10:26 (61), 12/21/2019 19:06 (3)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.