Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2023-20928 | First vendor Publication | 2023-01-26 |
Vendor | Cve | Last vendor Modification | 2023-02-06 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | |||
---|---|---|---|
Overall CVSS Score | 7.8 | ||
Base Score | 7.8 | Environmental Score | 7.8 |
impact SubScore | 5.9 | Temporal Score | 7.8 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | High |
Integrity Impact | High | Availability Impact | High |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
In binder_vma_close of binder.c, there is a possible use after free 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: AndroidVersions: Android kernelAndroid ID: A-254837884References: Upstream kernel |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-20928 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
50 % | CWE-667 | Insufficient Locking |
50 % | CWE-416 | Use After Free |
CPE : Common Platform Enumeration
Type | Description | Count |
---|---|---|
Os | 1 |
Sources (Detail)
Source | Url |
---|---|
MISC | http://packetstormsecurity.com/files/170855/Android-Binder-VMA-Management-Sec... https://source.android.com/security/bulletin/2023-01-01 |
Alert History
Date | Informations |
---|---|
2023-02-07 00:27:33 |
|
2023-02-02 00:27:13 |
|
2023-01-27 17:27:17 |
|
2023-01-27 00:27:14 |
|