CVE-2024-43093
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.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.
Also consider: patch
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-43093 being exploited?
Yes. CVE-2024-43093 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-43093?
CVE-2024-43093 is rated High with a CVSS score of 7.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-43093?
Yes. A fix has been recorded for CVE-2024-43093. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-43093 affect?
CVE-2024-43093 affects google:android. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected15
- affected14
- affected13
- affected12L
- affected12
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 13 Nov 2024 (SSVC 2.0.3).
timeline
- 7 Nov 2024Added to CISA KEV (exploited in the wild)
- 13 Nov 2024CISA SSVC assessment: exploitation active · 7 days later
- 13 Nov 2024Published · same day later
- 28 Nov 2024CISA remediation due date (US federal agencies) · 14 days later
- 21 Oct 2025CVE record last updated · 328 days (about 11 months) later
- 22 Oct 2026First proof-of-concept repository on GitHub (unvetted) · 365 days (about 1 year) later
- 2 Nov 2026Analysed by vulneraibility.com · 12 days later
- Linkandroid.googlesource.com /platform/frameworks/base/+/7f83c671626f9bf993581f4598c22482d87cba10
- Linksource.android.com /security/bulletin/2025-03-01
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-43093
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.