# CVE-2023-38302: Information disclosure in n/a

> Local apps can read Wi-Fi and Bluetooth MAC addresses from system properties, bypassing Android privacy restrictions on device identifiers.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2024
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-843f-6jw5-wr67

## What is CVE-2023-38302?

CVE-2023-38302 is a medium-severity vulnerability in n/a, published on 22 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A certain software build for the Sharp Rouvo V device (SHARP/VZW_STTM21VAPP/STTM21VAPP:12/SP1A.210812.016/1KN0_0_530:user/release-keys) leaks the Wi-Fi MAC address and the Bluetooth MAC address to system properties that can be accessed by any local app on the device without any permissions or special privileges. Google restricted third-party apps from directly obtaining non-resettable device identifiers in Android 10 and higher, but in this instance they are leaked by a high-privilege process and can be obtained indirectly. This malicious app reads from the "ro.boot.wifi_mac" system property to indirectly obtain the Wi-Fi MAC address and reads the "ro.boot.bt_mac" system property to obtain the Bluetooth MAC address.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-38302?


## How do I fix CVE-2023-38302?

No fix has been published for CVE-2023-38302 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-38302 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-38302 and fix it if it is affected.

What it is: CVE-2023-38302 is a medium-severity vulnerability in n/a, published on 22 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-38302 in the wild and no public exploit code.

Affected product: n/a. 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-2023-38302/ (Markdown: https://insights.sbomify.com/CVE-2023-38302/index.md)
```

## Sources

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

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