dbcve.org
AndroidOperating system · Google

CVE-2024-43765

HIGH · 7.8 CVSS v3.1 Published 2025-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 multiple locations, there is a possible way to obtain access to a folder due to a tapjacking/overlay attack. This could lead to local escalation of privilege with User 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 · moderate confidence

This is a tapjacking/overlay vulnerability in Android that allows attackers to intercept user taps by placing malicious overlays on top of legitimate UI elements. The flaw exists in multiple locations and enables unauthorized access to folders, resulting in local privilege escalation. Exploitation requires user interaction and user-level execution privileges.

MitigationImplement FLAG_SECURE on sensitive views to prevent screenshots and overlay captures, add touch-filtering checks using filterspoofingdetection, and ensure permission-sensitive operations verify the app is in the foreground before processing.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Verify Android version
    Go to Settings > About Phone and check the Android version field
    Affected if The version listed matches 12.0, 12.1, 13.0, 14.0, or 15.0 exactly
  2. Identify apps with overlay permission
    Go to Settings > Apps > Special app access > Display over other apps and review the list of apps granted this permission
    Affected if Any untrusted or unfamiliar apps are listed with the ability to draw overlays
  3. Check for system alert window permission usage
    Use adb shell dumpsys permission to query which apps hold the SYSTEM_ALERT_WINDOW permission
    Affected if Apps other than system apps or known accessibility tools possess this permission
  4. Review app foreground detection
    Inspect application code or use a security tool to verify whether permission-sensitive operations check if the app is in the foreground before executing
    Affected if Sensitive operations do not verify foreground status before processing input
  5. Audit custom overlays in installed apps
    Examine installed applications for any that create transparent windows or floating views that could intercept touches
    Affected if Applications create transparent or floating UI elements that could overlay other apps

You are affected if your device runs Android 12.0, 12.1, 13.0, 14.0, or 15.0 and has apps with overlay permissions installed that lack proper foreground verification and FLAG_SECURE protections.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement FLAG_SECURE on sensitive views to prevent screenshots and overlay captures, add touch-filtering checks using filterspoofingdetection, and ensure permission-sensitive operations verify the app is in the foreground before processing.

Recommended fix Moderate confidence

Android 15

  1. Upgrade the device to Android 15 or later to receive the security patch that addresses the tapjacking/overlay vulnerability.
  2. Verify the Android version after upgrade by navigating to Settings > About Phone > Android version to confirm the fix is applied.
  3. For enterprise or managed devices, ensure the MDM/EMM solution pushes the Android 15 update to all affected devices.
  4. If immediate upgrade is not possible, advise users to exercise caution when granting overlay permissions to untrusted applications and review app permissions regularly in Settings > Apps > Special app access > Display over other apps.
Caveat Android 15 may introduce compatibility changes for older apps; verify critical business applications are compatible before mass deployment

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

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43765 — 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-43765 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