How severe is CVE-2024-43093?

CVE-2024-43093 has a CVSS score of 7.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-43093?

Affected package information for CVE-2024-43093 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2024-43093?

No fixed version has been published for CVE-2024-43093 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2024-43093 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2024-43093, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-43093?

CVE-2024-43093 has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 34th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2024-43093 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2024-43093 (Android Framework Privilege Escalation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2024-11-07. CISA required all US federal civilian agencies to remediate this vulnerability by 2024-11-28. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2024-43093?

CVE-2024-43093 is classified as CWE-176 (CWE-176). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2024-43093?

CVE-2024-43093 affects google android (5 versions, e.g. 12.0, 12.1, 13.0…). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2024-43093 published, and has it been updated?

CVE-2024-43093 was published on November 13, 2024 and was last updated on October 23, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2024-11-07 — agencies required to remediate by 2024-11-28

CVE-2024-43093

HIGH

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…

Published

Nov 13, 2024

Updated

Oct 23, 2025

Affected

0 pkgs

Patched

None yet

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk34th percentile0.00%

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.

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 Products

1 product · 5 configurations

androidgoogle

5 versions

12.012.113.014.015.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In shouldHideDocument of ExternalStorageProvider.java, there is a possib…

cisa.govCISANov 2024

In shouldHideDocument of ExternalStorageProvider.java, there is a possib…

github.comGithubNov 2024

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-43093 in your stack?

O3 detects CVE-2024-43093 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works