# CVE-2020-0463: Information disclosure in Android

> A missing bounds check in the Android Bluetooth SDP server allows remote attackers to read sensitive memory without user interaction or privileges.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** A-169342531, ASB-A-169342531, GHSA-8jw9-px85-866f

## What is CVE-2020-0463?

CVE-2020-0463 is a high-severity vulnerability in Google Android, published on 14 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In sdp_server_handle_client_req of sdp_server.cc, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information disclosure from the bluetooth server with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-8.0 Android-8.1 Android-9Android ID: A-169342531

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2020-0463?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2020-0463?

Apply the vendor's patch.

## Is CVE-2020-0463 being exploited?

There is no known exploitation of CVE-2020-0463 in the wild and no public exploit code.

Public exploit code:

- https://github.com/nanopathi/system_bt_AOSP10_r33_CVE-2020-0463 (github_poc): https://github.com/nanopathi/system_bt_AOSP10_r33_CVE-2020-0463

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-0463 and fix it if it is affected.

What it is: CVE-2020-0463 is a high-severity vulnerability in Google Android, published on 14 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-0463 in the wild and no public exploit code.

Affected product: Google Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-0463/ (Markdown: https://insights.sbomify.com/CVE-2020-0463/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-0463
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-0463
- OSV: https://osv.dev/vulnerability/CVE-2020-0463

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-0463/
Summaries are generated and may contain mistakes; the official description above is the record.