dbcve.org
AndroidOperating system · Google

CVE-2024-49734

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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 functions of ConnectivityService.java, there is a possible way for a Wi-Fi AP to determine what site a device has connected to through a VPN due to side channel information disclosure. This could lead to remote information disclosure 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

A vulnerability in Android's ConnectivityService.java allows a malicious Wi-Fi Access Point to perform side-channel traffic analysis to determine which sites a device is accessing, even when connected through a VPN. The issue stems from information leakage in multiple functions that exposes timing or traffic patterns that reveal VPN tunnel destinations.

MitigationApply available Android security patches; until a patch is available, users should avoid connecting to untrusted Wi-Fi networks when using VPNs.

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:= 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if Version equals 14.0 or 15.0 exactly
  2. Verify Wi-Fi connectivity
    Check that Wi-Fi is enabled and the device is connected to a network via Settings > Network & Internet > Wi-Fi, or run 'dumpsys wifi' via ADB
    Affected if Wi-Fi is enabled and connected to any network (the malicious AP scenario requires an active Wi-Fi connection)
  3. Confirm VPN is active
    Check for active VPN connections in Settings > Network & Internet > VPN, or run 'dumpsys vpn' via ADB
    Affected if A VPN tunnel is active - the vulnerability allows traffic analysis to determine VPN destination sites even when encrypted

You are affected if your device runs Android 14.0 or 15.0 and you use Wi-Fi while connected to a VPN, because the vulnerability enables a malicious Wi-Fi access point to infer VPN tunnel destinations through timing or traffic pattern leakage.

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

Apply available Android security patches; until a patch is available, users should avoid connecting to untrusted Wi-Fi networks when using VPNs.

Recommended fix Moderate confidence

Android 14 and 15 devices should receive the November 2024 Security Patch Level (SPL) update or later. For additional protection, Android 16 (when available) includes this fix.

  1. Ensure the device is running Android 14 or 15, then navigate to Settings > Security & privacy > Security update > Check for update
  2. Apply the latest Android Security Patch Level (SPL) update. For CVE-2024-49734, this was addressed in the November 2024 Android Security Bulletin (or subsequent patches)
  3. Verify the fix by confirming the Security Patch Level in Settings > About Phone > Android version shows the November 2024 update or later
  4. For enterprise-managed devices, ensure the device management software deploys the November 2024 (or later) security patch to all affected Android 14 and 15 devices
Caveat Standard Android monthly security updates typically do not introduce breaking changes; they are backward-compatible. However, verify with OEM device vendors for any specific implementation notes.

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

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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