dbcve.org
AndroidOperating system · Google

CVE-2024-43763

MEDIUM · 6.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 →
70/100
Remediation priority · Elevated
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 build_read_multi_rsp of gatt_sr.cc, there is a possible denial of service due to a logic error in the code. This could lead to remote (proximal/adjacent) denial of service 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 confidence

A logic error in the build_read_multi_rsp function of the Bluetooth GATT server (gatt_sr.cc) causes a denial of service condition when processing multi-read responses. An attacker within Bluetooth range can exploit this flaw to crash or freeze the Bluetooth stack on the target device without any authentication or user interaction.

MitigationApply the vendor-supplied security patch for CVE-2024-43763 to the affected Android device. Users should ensure their devices receive regular system updates to receive fixes for Bluetooth stack vulnerabilities.

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check your Android version
    Go to Settings > About Phone > Android version. Confirm the exact version number displayed matches 12.0, 12.1, 13.0, 14.0, or 15.0.
    Affected if The displayed version is exactly 12.0, 12.1, 13.0, 14.0, or 15.0.
  2. Verify Bluetooth is enabled
    Go to Settings > Bluetooth and confirm the toggle is switched on.
    Affected if Bluetooth is currently enabled on the device.
  3. Check if Bluetooth is in discoverable or connectable mode
    In Settings > Bluetooth, look at your device name and whether other devices can discover or pair with it. Also check Settings > Connected devices > Connection preferences > Bluetooth visibility.
    Affected if Bluetooth visibility is set to on or your device is discoverable to other Bluetooth devices.
  4. Review Bluetooth stack behavior
    Check for recent unexplained Bluetooth crashes, freezes, or automatic disconnections. Look in Settings > About Phone > Bug reports or check logcat output for Bluetooth-related errors involving gatt_sr.cc or GATT server messages.
    Affected if The Bluetooth stack has recently crashed, frozen, or exhibited unstable behavior after being within Bluetooth range of other devices.
  5. Confirm GATT server exposure
    Check if your device is running any BLE GATT services that accept read requests. In developer options, enable Bluetooth HCI snoop log and analyze with btsnooz.py or Wireshark to observe GATT interaction patterns.
    Affected if Your device exposes GATT services or responds to multi-read GATT requests from nearby devices.

You are affected if your device runs Android 12.0, 12.1, 13.0, 14.0, or 15.0 with Bluetooth enabled and exposed to nearby attackers.

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 the vendor-supplied security patch for CVE-2024-43763 to the affected Android device. Users should ensure their devices receive regular system updates to receive fixes for Bluetooth stack vulnerabilities.

Recommended fix High confidence

Upgrade to Android 15 or latest stable release with current security patches

  1. 1. Back up all important data from the Android device
  2. 2. Navigate to Settings > System > Software Update (or Settings > About Phone > System Update)
  3. 3. Check for available updates and download the latest Android security patch level
  4. 4. Install the update and restart the device
  5. 5. Verify the device is running a security patch level that includes the fix for CVE-2024-43763 (refer to Android Security Bulletin for the specific patch date)
Caveat Upgrading major Android versions (e.g., 14 to 15) may cause compatibility issues with older apps or require reconfiguration of device settings

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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