# CVE-2020-13702: Information disclosure in n/a

> Attackers can track individual device movement via Bluetooth LE due to a secondary temporary UID in the Exposure Notification API.

- **Severity:** Medium 4.3 (`CVSS:3.1/AC:L/AV:A/A:N/C:L/I:N/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-49fh-5689-5m82

## What is CVE-2020-13702?

CVE-2020-13702 is a medium-severity vulnerability in n/a, published on 11 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Rolling Proximity Identifier used in the Apple/Google Exposure Notification API beta through 2020-05-29 enables attackers to circumvent Bluetooth Smart Privacy because there is a secondary temporary UID. An attacker with access to Beacon or IoT networks can seamlessly track individual device movement via a Bluetooth LE discovery mechanism.

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

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

It affects 1 product.


Products: The Rolling Proximity Identifier Project the Rolling Proximity Identifier.

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

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

## Is CVE-2020-13702 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-13702 is a medium-severity vulnerability in n/a, published on 11 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-13702 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-2020-13702/ (Markdown: https://insights.sbomify.com/CVE-2020-13702/index.md)
```

## Sources

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

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