CVE-2023-40129

Adjacent code execution via Bluetooth length underflow

Published Oct 27, 2023 · Updated Sep 9, 2024

Heap buffer overflow in Google Android 12, 12L, and 13 allows remote attackers to execute code over an adjacent Bluetooth connection. In build_read_multi_rsp in gatt_sr.cc, a variable-length response can make a length subtraction underflow when the buffered length equals MTU minus one, leading to an out-of-bounds heap write. The flaw requires Bluetooth proximity but no authentication, additional execution privileges, or user interaction, and successful exploitation executes code on the device.

CVSS severity8.8
High
EPSS probability0.22%
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

Heap buffer overflow in Google Android 12, 12L, and 13 allows remote attackers to execute code over an adjacent Bluetooth connection. In build_read_multi_rsp in gatt_sr.cc, a variable-length response can make a length subtraction underflow when the buffered length equals MTU minus one, leading to an out-of-bounds heap write. The flaw requires Bluetooth proximity but no authentication, additional execution privileges, or user interaction, and successful exploitation executes code on the device.

The record

CVE
CVE-2023-40129
Published
Oct 27, 2023
Updated
Sep 9, 2024
Vendor
Google
Product
Android
Classifications
CWE-787, T1210
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Oct 27, 2023CVE publishedPublication date reported by the CVE source.
  2. Sep 9, 2024Record 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

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

Published CVSS scores

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-787Out-of-bounds Write
T1210Exploitation of Remote Services

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