Security Advisory

CVE-2024-34722: Android BLE Legacy Pairing Auth Bypass

Last updated:
  • CVE-2024-34722

CVE-2024-34722 is an authentication bypass in the Android Bluetooth stack's LE legacy pairing: smp_proc_rand accepted the peer's random value before the device had sent its own confirm value, so a nearby attacker could complete pairing without the check. NVD scores it 8.8. Android 12 to 14 are affected; patch level 2025-01-01 fixes it.

Vulnerability summary

CVSS base score

8.8

High severity

EPSS score (FIRST)

0.2%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2024-34722 · Source: NVD

Affected components

ComponentCPEVersion range
Android Bluetooth stack (Security Manager Protocol, smp_act.cc)cpe:2.3:o:google:android:14.0:*:*:*:*:*:*:*Android 12, 12L, 13 and 14 (Android CNA record; NVD CPEs list 12.0, 12.1, 13.0, 14.0); fixed at security patch level 2025-01-01 (Android Security Bulletin, January 2025)
Android-based devices from OEMs (phones, tablets, handhelds, panels and other products on AOSP 12 to 14)—affected until the OEM ships a build with security patch level 2025-01-01 or later; the fix is not listed as a Google Play system update

What does this mean for affected devices?

NVD's description: "In smp_proc_rand of smp_act.cc, there is a possible authentication bypass during legacy BLE pairing due to incorrect implementation of a protocol. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation." NVD's Primary score is CVSS v3.1 8.8 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) with no CWE of its own (NVD-CWE-noinfo). The Android CNA published no CVSS score; CISA's ADP entry scores it 7.4 (AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) and maps it to CWE-303, incorrect implementation of an authentication algorithm. NVD's CPEs list Android 12.0, 12.1, 13.0 and 14.0, and the record was published on 2024-07-09 (NVD, CVE record).

Which Android bulletin fixes it?

NVD links two bulletins. The July 2024 bulletin (version 1.0, 1 July 2024) does not list CVE-2024-34722, and NVD tags that reference "Not Applicable". The January 2025 Android Security Bulletin lists it in the System section at the 2025-01-01 security patch level: type EoP, severity High, AOSP versions 12, 12L, 13 and 14, bug A-251514170 with two Bluetooth module changes. It is not in that bulletin's Google Play system updates table, so a device gets the fix only through an OEM build at patch level 2025-01-01 or later.

What does the fix change?

In LE legacy pairing each side sends a confirm value and then reveals the random value behind it. The change linked from the bulletin, titled "Fix an authentication bypass bug in SMP", says that "when pairing with BLE legacy pairing initiated from remote, authentication can be bypassed". It sets a flag when the local confirm is sent and makes smp_proc_rand fail pairing with invalid parameters if, in legacy pairing (either side lacks Secure Connections support), the peer's random value arrives before that flag is set. Pairing where both sides use LE Secure Connections does not take this path.

Which devices does it affect?

The code runs on the Android side, so the exposure is any product built on AOSP 12 to 14 with Bluetooth enabled: phones and tablets, and also Android-based handhelds, kiosks, panels and similar devices whose maker controls the patch level. Check the security patch level in the device settings or build properties; anything earlier than 2025-01-01 lacks the fix. A BLE peripheral that requires LE Secure Connections pairing avoids the legacy path on its own links, but it cannot repair an unpatched phone. Our Bluetooth LE security guide explains why LE legacy pairing is weak even without this bug, CVE-2022-25836 covers the specification-level Passkey Entry problem, and CVE-2024-8805 is a 2024 pairing-confirmation flaw in the Linux stack. The authentication bypass fix guide covers the class.

CVE-2024-34722 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.00248, the 16th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).

How to fix this class of issueThis advisory's weakness class is Authentication bypass. Our practical guide covers how to detect, fix, verify and disclose it: How to fix authentication bypass in embedded firmware.

Evidence

  • NVD: smp_proc_rand of smp_act.cc, possible authentication bypass during legacy BLE pairing due to incorrect implementation of a protocol; remote EoP, no user interaction. NVD Primary CVSS v3.1 8.8 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; NVD-CWE-noinfo; CISA-ADP 7.4 AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-303; CPEs android 12.0, 12.1, 13.0, 14.0; published 2024-07-09; references July 2024 bulletin (tag Not Applicable), January 2025 bulletin, commit 456f705b. — NVD
  • CVE record (assigner google_android): affected Android 12, 12L, 13, 14, default unaffected; CNA gives no CVSS metric; CISA-ADP 7.4 and CWE-303. — CVE.org
  • Android Security Bulletin January 2025 (published January 6, 2025, updated February 6, 2025): 2025-01-01 security patch level, System: CVE-2024-34722 A-251514170 [2], EoP, High, 12, 12L, 13, 14. Google Play system updates table lists only Documents UI and Permission Controller for this patch level. — Android
  • Android Security Bulletin July 2024 (version 1.0, July 1, 2024) does not list CVE-2024-34722. — Android
  • Commit 317b4e29 'Fix an authentication bypass bug in SMP': 'When pairing with BLE legacy pairing initiated from remote, authentication can be bypassed.' Bug 251514170. Adds SMP_PAIR_FLAGS_CMD_CONFIRM_SENT; smp_proc_rand returns SMP_INVALID_PARAMETERS when not both sides support SC and the local confirm has not been sent ('in legacy pairing, the peer should send its rand after we send our confirm'). — AOSP (googlesource)
  • CVE-2024-34722 is not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
  • EPSS 0.00248, percentile 0.16225, dataset 2026-11-17. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CVE record: CVE-2024-34722
  3. Android Security Bulletin, January 2025
  4. Android Security Bulletin, July 2024
  5. AOSP Bluetooth: Fix an authentication bypass bug in SMP (A-251514170)
  6. CISA KEV
  7. FIRST EPSS

Frequently asked questions

Which Android versions are affected by CVE-2024-34722?

Android 12, 12L, 13 and 14. The January 2025 Android Security Bulletin lists the fix at the 2025-01-01 security patch level, so a device on any of those versions needs that patch level or later (per the Android CNA record and the January 2025 bulletin).

Was CVE-2024-34722 fixed in the July 2024 Android bulletin?

No. NVD links the July 2024 bulletin but tags it Not Applicable, and that bulletin does not list the CVE. The January 2025 bulletin is the one that lists it, under bug A-251514170 (per NVD and the two bulletins).

Does LE Secure Connections pairing avoid CVE-2024-34722?

The fix only adds the check when the two sides are not both using Secure Connections, so the flaw sits in the LE legacy pairing path. A peripheral that insists on Secure Connections keeps its own links off that path, but the Android device still needs the patch (per the AOSP change linked from the bulletin).

Is CVE-2024-34722 in the CISA KEV catalog?

No, not as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.00248, the 16th percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).