CVE-2020-13702: The Rolling Proximity Identifier used in the Apple/Google Exposure Notification API beta through 2020-05-29 en

Q: How do I fix CVE-2020-13702?

the rolling proximity identifier: upgrade to newer than 2020-05-29. Exact commands for each OS are on this page.

Q: Is CVE-2020-13702 being exploited?

CVE-2020-13702 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-13702 affect?

CVE-2020-13702 affects the rolling proximity identifier. Severity is medium (CVSS 4.3). 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 Beaco

Q: How urgent is CVE-2020-13702?

Priority 41/100. Public exploit reference

This month

MEDIUM 4.3UPGRADE

CVE-2020-13702 is a medium-severity flaw (CVSS 4.3) affecting the rolling proximity identifier. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.2% (top 17%)
CISA exploited list	No
Weakness	CWE-200
Published	2020-06-11
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: the rolling proximity identifier project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-06-11 19:15 UTCPublished CVE record published
2026-06-17 02:53 UTCUpdated Record last modified

the rolling proximity identifier project the rolling proximity identifier UPGRADE

Affected: <= 2020-05-29

Fixed in: newer than 2020-05-29

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy the-rolling-proximity-identifier || rpm -q the-rolling-proximity-identifier || the-rolling-proximity-identifier --version

2. UPGRADE to newer than 2020-05-29 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade the-rolling-proximity-identifier

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade the-rolling-proximity-identifier

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-13702?

the rolling proximity identifier: upgrade to newer than 2020-05-29. Exact commands for each OS are on this page.

Is CVE-2020-13702 being exploited?

CVE-2020-13702 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-13702 affect?

CVE-2020-13702 affects the rolling proximity identifier. Severity is medium (CVSS 4.3). 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 Beaco

How urgent is CVE-2020-13702?

Priority 41/100. Public exploit reference

Software pages

Bluetooth vulnerabilities

References

← Back to latest CVEs