CVERadar
HIGH · CVSS 3.1 7.3CISA KEV · added 2024-11-07EPSS 0.71% (p53)Threat level 52

CVE-2024-43093: Android Framework Privilege Escalation Vulnerability

Android · Framework · NVD published 2024-11-14 · posted 2024-11-07 · last modified 2026-06-17

What it is

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.

WeaknessCWE-176
CVSS vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H (source: [email protected])
CISA due date2024-11-28 (for US federal agencies under BOD; a good deadline for everyone)
ATT&CK tacticsn/a

Exploitation evidence

First exploit evidence seen: 2024-11-07 (earliest date across the sources below).

Exploited in the wild

  • CISA KEV: listed since 2024-11-07. Source

Public exploit code

GitHub proof-of-concept repositories below quality bar

1 public repositories from 1 accounts, first seen 2026-10-22.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: CISA KEV · nomi-sec/PoC-in-GitHub.

No ATT&CK techniques could be mapped or inferred for this CVE yet.

How to fix it

CISA required action

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (source: CISA KEV)

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources