CVE-2023-35681
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 · uneditedIn eatt_l2cap_reconfig_completed of eatt_impl.h, there is a possible out of bounds write due to an integer overflow. This could lead to remote code execution 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 · high confidenceA critical integer overflow vulnerability exists in the eatt_l2cap_reconfig_completed function within Android's Bluetooth stack (eatt_impl.h). The overflow allows an attacker to write beyond allocated buffer boundaries, leading to arbitrary code execution. Since no authentication or user interaction is required, this can be exploited remotely over Bluetooth.
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= 13.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Android versionNavigate to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if The displayed version is exactly 13.0 (Android 13)
-
Verify Bluetooth is enabledCheck Settings > Bluetooth is turned ON, or run 'settings get global bluetooth_on' via ADBAffected if Bluetooth is actively enabled on the device
-
Confirm EATT feature is in useEATT (Enhanced Attribute Protocol) is typically used when a device connects using Bluetooth 5.0+ LE; check connected Bluetooth devices and their protocol versions via 'adb shell dumpsys bluetooth_manager'Affected if Bluetooth 5.0 or higher LE connections are established with EATT enabled
-
Review Bluetooth stack logs for anomaliesRun 'adb logcat | grep -i eatt' or 'adb logcat | grep -i l2cap' to search for error messages related to the vulnerable code pathAffected if Unexpected errors, buffer warnings, or crashes appear in logs mentioning eatt_l2cap_reconfig_completed or buffer overflows
A device is affected if it runs Android 13.0 with Bluetooth enabled and actively using EATT/L2CAP connections, as the integer overflow in eatt_l2cap_reconfig_completed only triggers during Bluetooth operations on this specific Android version.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the Android security patch (June 2023 or later) which addresses this vulnerability. For custom Android builds, audit and fix the bounds checking in the eatt_l2cap_reconfig_completed function to prevent integer overflow in size calculations.
Android 13.0 with latest security patch level (December 2023 or later recommended)
- 1. Go to Settings on the Android 13.0 device
- 2. Navigate to System > Software Update (or Settings > About Phone > System Update)
- 3. Check for updates and download any available updates
- 4. Install the latest Android security patch update
- 5. Verify the update was successful by checking the Android Security Patch Level in Settings > About Phone > Android version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35681 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-35681 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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