CVE-2024-43093
CVE-2024-43093 is a CWE-176 vulnerability in platform/frameworks/base. It is in CISA's Known Exploited Vulnerabilities catalog (added 2024-11-07) — treat it as actively exploited and patch now. O3 Security confirms whether CVE-2024-43093 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2024-11-07. Federal agencies were required to remediate by 2024-11-28.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2024-43093.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
platform/frameworks/base📦platform/frameworks/base📦platform/frameworks/base📦platform/frameworks/base📦platform/frameworks/base📦platform/frameworks/baseReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Android packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦Android | platform/frameworks/base | ≥ 15-next:0&&< 15-next:2025-03-01 | 15-next:2025-03-01 |
| 📦Android | platform/frameworks/base | ≥ 12:0&&< 12:2025-03-01 | 12:2025-03-01 |
| 📦Android | platform/frameworks/base | ≥ 12L:0&&< 12L:2025-03-01 | 12L:2025-03-01 |
| 📦Android | platform/frameworks/base | ≥ 15:0&&< 15:2025-03-01 | 15:2025-03-01 |
| 📦Android | platform/frameworks/base | ≥ 13:0&&< 13:2025-03-01 | 13:2025-03-01 |
| 📦Android | platform/frameworks/base | ≥ 14:0&&< 14:2025-03-01 | 14:2025-03-01 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for platform/frameworks/base. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update platform/frameworks/base to 15-next:2025-03-01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-43093 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-43093 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2024-43093. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-43093 in your dependencies?
O3 detects CVE-2024-43093 across Android dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.