Google Android Access Control /persist/ access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android. It has been classified as critical. The impacted element is an unknown function of the file /persist/ of the component Access Control. Performing a manipulation results in access control. This vulnerability is reported as CVE-2018-11910. The attack requires a local approach. No exploit exists. It is recommended to apply a patch to fix this issue.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (unknown version). It has been classified as critical. This affects an unknown code block of the file /persist/ of the component Access Control. 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:
In all android releases(Android for MSM, Firefox OS for MSM, QRD Android) from CAF using the linux kernel, improper access control can lead to device node and executable to be run from /persist/ which presents a potential issue.
The bug was discovered 11/05/2018. The weakness was disclosed 11/27/2018 (Website). It is possible to read the advisory at source.codeaurora.org. This vulnerability is uniquely identified as CVE-2018-11910 since 06/07/2018. The exploitability is told to be easy. Attacking locally is a requirement. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 22 days. During that time the estimated underground price was around $5k-$25k.
Applying a patch is able to eliminate this problem.
The entries VDB-127164, VDB-127165, VDB-127166 and VDB-127176 are pretty similar. Be aware that VulDB is the high quality source 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: 🔍
0-Day Time: 🔍
Patch: source.codeaurora.org
Timeline
06/07/2018 🔍11/05/2018 🔍
11/27/2018 🔍
11/27/2018 🔍
11/28/2018 🔍
06/11/2023 🔍
Sources
Vendor: google.comAdvisory: source.codeaurora.org
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-11910 (🔍)
GCVE (CVE): GCVE-0-2018-11910
GCVE (VulDB): GCVE-100-127167
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 11/28/2018 07:53Updated: 06/11/2023 15:24
Changes: 11/28/2018 07:53 (60), 04/15/2020 10:02 (2), 06/11/2023 15:24 (4)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.