dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 28 Nov 2024.
AndroidOperating system · Google

CVE-2024-43093

HIGH · 7.3 CVSS v3.1 Published 2024-11-13
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
94/100
Remediation priority · Urgent
In the wild Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a local privilege escalation vulnerability in Android's ExternalStorageProvider. The shouldHideDocument function contains a unicode normalization error that allows attackers to bypass file path filters protecting sensitive directories. By using specific unicode characters in file paths, malicious applications can access protected directories they normally couldn't reach.

MitigationApply the Android system security patch (typically part of Android's monthly security bulletins). For enterprises, review and enforce MDM policies restricting external storage access until patches are deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:= 12.0= 12.1= 13.0= 14.0= 15.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Android OS version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if The version shows 12.0, 12.1, 13.0, 14.0, or 15.0 (specifically any of the listed affected versions) and the security patch level is earlier than the fix for CVE-2024-43093
  2. Verify ExternalStorageProvider component exists
    Check for the presence of the ExternalStorageProvider APK or system service via 'dumpsys package externalstorageprovider' or by inspecting /system/priv-app/ExternalStorageProvider (path may vary by device)
    Affected if The ExternalStorageProvider component is present on the device, indicating the vulnerable code path exists
  3. Check security patch level
    Run 'getprop ro.build.version.security_patch' via ADB or check Settings > About Phone > Security patch level
    Affected if The security patch level predates the September 2024 Android security update (or whichever patch contains the fix for CVE-2024-43093)

If the device runs Android 12.0 through 15.0 and lacks the corresponding security patch for CVE-2024-43093, the environment is vulnerable to the Unicode path filter bypass in ExternalStorageProvider.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch android.googlesource.com →
Interim mitigation

Apply the Android system security patch (typically part of Android's monthly security bulletins). For enterprises, review and enforce MDM policies restricting external storage access until patches are deployed.

Recommended fix Moderate confidence

Android 15.0 or later; alternatively, apply the latest Android Security Patch Level containing the CVE-2024-43093 fix from your device manufacturer

  1. 1. Verify the current Android version on affected devices (Settings > About Phone > Android version)
  2. 2. For Android 12.0, 12.1, 13.0, and 14.0 devices: Apply the latest Android Security Patch Level available from your device manufacturer
  3. 3. If available, upgrade devices to Android 15.0 which contains the fix for this vulnerability
  4. 4. Verify the fix is applied by checking that the Security Patch Level is after the release date of the CVE fix (refer to Android Security Bulletin)
Caveat Android 15 upgrade may introduce behavior changes; ensure compatibility testing with your applications before broad deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Exploited in the wild — priority engagement
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43093 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43093 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data