CVE-2024-43093: Android Framework Privilege Escalation
Android Framework · listed in the CISA catalog of actively exploited vulnerabilities since 2024-11-07.
- CVSS v3.1 (CISA ADP)
- 7.3
- high
- EPSS (exploit probability, 30 days)
- 0.7%
- higher than 54.4% of all CVEs
- Added to CISA KEV
- 2024-11-07
- US federal due date 2024-11-28
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2024-43093 explained
CVE-2024-43093 is a privilege escalation flaw in the Android Framework, in shouldHideDocument of ExternalStorageProvider.java. Incorrect unicode normalization can bypass a file path filter meant to block access to sensitive directories. CISA lists it as known to be exploited, so affected devices need prompt attention.
Impact
A local attacker with low privileges, such as a malicious app, could gain elevated privileges on the device without needing additional execution privileges. User interaction is required. The impact on confidentiality, integrity and availability is high. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so mass exploitation without manual steps is less likely. Attackers are known to use this vulnerability.
Who is affected
The CVE record lists Google Android versions 12, 12L, 13, 14 and 15 as affected. The CVE record names no fixed version. Check the vendor advisory to find the security patch level that addresses this issue for each Android version.
Written with AI from the data on this page and checked against it automatically.
Official description
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.
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Google AndroidAffectedFixed in
- 12
- 12L
- 13
- 14
- 15
not stated
| Product | Affected | Fixed in |
|---|---|---|
| Google Android |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: source.android.com/security/bulletin/2025-03-01
- CISA's deadline for US federal agencies: 2024-11-28 (passed) – a useful benchmark for everyone else, too.
What to do
- Check the Android vendor security advisory for the patch level that fixes CVE-2024-43093.
- Install the latest available Android security update on all managed devices running
12,12L,13,14or15. - Use device management to enforce minimum security patch levels and identify devices that have not updated.
- Restrict app installation to trusted sources to reduce the risk of malicious local apps.
- Follow CISA's required action: apply vendor mitigations or discontinue use of devices where mitigations are unavailable.
The CVE record names no fixed version, which does not mean no fix exists. Consult the vendor advisory for the relevant security patch level. Per CISA, apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Until devices are patched, limit app installs to trusted sources and monitor for unusual app behavior.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-176 Improper Handling of Unicode Encoding
Questions about CVE-2024-43093
- Is CVE-2024-43093 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-11-07, with a US federal due date of 2024-11-28. Whether it is used in ransomware campaigns is unknown.
- Can it be exploited remotely?
- No. The attack vector is local, requires low privileges and needs user interaction. CISA rates it as not automatable.
- Which Android versions are affected?
- The CVE record lists Google Android
12,12L,13,14and15. It names no fixed version, so refer to the vendor advisory for the patch level.
Written with AI from the data on this page and checked against it automatically.
References
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.