CVE-2024-43093
Android Framework Privilege Escalation Vulnerability
Android Framework
In shouldHideDocument of ExternalStorageProvider.java, there is a possible bypass of a file path filter designed to prevent access to sensitive directories due to incorrect unicode normalization. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 7 November 2024. US federal agencies were required to remediate it by 28 November 2024.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 0.7%, which is higher than 53.7% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2024-43093 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2024-43093.
What does CVE-2024-43093 affect?
CVE-2024-43093 affects Android Framework. In shouldHideDocument of ExternalStorageProvider.java, there is a possible bypass of a file path filter designed to prevent access to sensitive directories due to incorrect unicode normalization. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
How severe is CVE-2024-43093?
CVE-2024-43093 is rated HIGH with a CVSS base score of 7.3. EPSS puts the probability of exploitation in the next 30 days at 0.7%, higher than 53.7% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 28 November 2024.
How should organisations respond to CVE-2024-43093?
Apply the vendor patch for Android Framework as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.