CVE-2024-34722

Privilege escalation via out-of-order BLE pairing

Published Jul 9, 2024 · Updated Jan 21, 2025

Authentication bypass in Google Android 12 through 14 allows physically proximate attackers to gain elevated privileges through legacy BLE pairing. The smp_proc_rand function accepts a peer random value before the local confirm command is sent, violating the legacy pairing sequence. An unauthenticated attacker within BLE range can initiate pairing without user interaction and complete authentication out of order.

CVSS severity8.8
High
EPSS probability0.25%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authentication bypass in Google Android 12 through 14 allows physically proximate attackers to gain elevated privileges through legacy BLE pairing. The smp_proc_rand function accepts a peer random value before the local confirm command is sent, violating the legacy pairing sequence. An unauthenticated attacker within BLE range can initiate pairing without user interaction and complete authentication out of order.

The record

CVE
CVE-2024-34722
Published
Jul 9, 2024
Updated
Jan 21, 2025
Vendor
Google
Product
Android
Classifications
CWE-303
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 9, 2024CVE publishedPublication date reported by the CVE source.
  2. Jan 21, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=12
  2. Affected versionversion=12.0
  3. Affected versionversion=12l
  4. Affected versionversion=12L
  5. Affected versionversion=13
  6. Affected versionversion=13.0
  7. Affected versionversion=14
  8. Affected versionversion=14.0

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Google · Androidversion=12; version=12.0; version=12l; version=12L; version=13; version=13.0; version=14; version=14.0

Published CVSS scores

7.4CISA-ADPCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
8.8NIST NVDCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-303Incorrect Implementation of Authentication Algorithm

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo