dbcve.org
AndroidOperating system · Google

CVE-2024-11624

HIGH · 7.8 CVSS v3.1 Published 2025-01-03
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
there is a possible to add apps to bypass VPN due to Undeclared Permission . This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not 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 mobile (likely Android) vulnerability where an undeclared permission allows an application to bypass VPN protections, enabling local privilege escalation without user interaction. The issue stems from missing or improper permission declarations that should control VPN routing behavior.

MitigationThe fix requires proper declaration and enforcement of permissions related to VPN routing. Application developers must audit permission usage and ensure VPN bypass capabilities are protected by appropriate permission checks, or OS-level patch may be needed.

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:all versions

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. Check Android security patch level
    Go to Settings > About Phone > Security Patch Level and note the date. Compare this date against the month/year when the fix for CVE-2024-11624 was released by Google.
    Affected if The device has not received the OS-level security patch that enforces proper VPN permission declarations.
  2. Identify apps with VPN bypass capability
    Review installed applications, particularly pre-installed or system apps, that have network routing capabilities. Use a mobile security tool or adb command 'pm list packages' to enumerate apps, then inspect their AndroidManifest.xml files for permission declarations.
    Affected if An app possesses the ability to route traffic outside the VPN tunnel without proper permission checks being enforced by the OS.
  3. Verify VPN enforcement in network settings
    Navigate to Settings > Network & Internet > VPN and confirm that the VPN connection is active and routing traffic. Check if any apps have bypassed the VPN by reviewing per-app VPN settings if available.
    Affected if Traffic is being routed outside the VPN tunnel despite VPN being enabled, indicating the permission enforcement is not working.
  4. Check for unauthorized permission usage
    Use adb to inspect app permissions: 'dumpsys package <package_name>' for suspicious apps. Look for apps holding permissions related to VPN routing or network configuration that should require elevated privilege.
    Affected if An app holds permissions that allow VPN bypass due to missing or improper permission declarations in the Android framework.

The environment is affected if the Android device is running a version without the security patch that enforces proper VPN routing permission declarations, or if network traffic is being routed outside the VPN tunnel despite VPN being enabled.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

The fix requires proper declaration and enforcement of permissions related to VPN routing. Application developers must audit permission usage and ensure VPN bypass capabilities are protected by appropriate permission checks, or OS-level patch may be needed.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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