Google Android inode.c sdcardfs_create/sdcardfs_mkdir access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android. It has been classified as critical. Impacted is the function sdcardfs_create/sdcardfs_mkdir of the file inode.c. The manipulation leads to access control.
This vulnerability is referenced as CVE-2018-9515. The attack can only be performed from a local environment. Furthermore, an exploit is available.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (unknown version) and classified as critical. This issue affects the function sdcardfs_create/sdcardfs_mkdir of the file inode.c. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In sdcardfs_create and sdcardfs_mkdir of inode.c, there is a possible memory corruption due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android Versions: Android kernel Android ID: A-111641492 References: N/A
The bug was discovered 10/01/2018. The weakness was published 10/02/2018 (Website). The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2018-9515 since 04/05/2018. An attack has to be approached locally. The requirement for exploitation is a simple authentication. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The exploit is available at exploit-db.com. It is declared as proof-of-concept. 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.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the databases at Exploit-DB (45558) and SecurityFocus (BID 105483†). Similar entries are available at VDB-124743 and VDB-124744. 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: 6.5VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
04/05/2018 🔍10/01/2018 🔍
10/01/2018 🔍
10/02/2018 🔍
10/02/2018 🔍
10/03/2018 🔍
06/06/2024 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-9515 (🔍)
GCVE (CVE): GCVE-0-2018-9515
GCVE (VulDB): GCVE-100-124745
SecurityFocus: 105483 - Google Android Kernel Components Multiple Privilege Escalation Vulnerabilities
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 10/03/2018 08:13Updated: 06/06/2024 10:14
Changes: 10/03/2018 08:13 (63), 03/29/2020 12:23 (7), 06/06/2024 10:14 (17)
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.