dbcve.org
The Rolling Proximity IdentifierApplication · The Rolling Proximity Identifier Project

CVE-2020-13702

CRITICAL · 10.0 CVSS v3.1 Published 2020-06-11
Fix available
A fix is available. Upgrade to after 2020-05-29 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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
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.

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

The Apple/Google Exposure Notification API's Rolling Proximity Identifier contains a secondary static temporary UID that persists beyond the rotating primary identifier. This allows attackers with Bluetooth LE access (via Beacon or IoT networks) to track individual device movement by correlating the static secondary UID, effectively bypassing the Bluetooth Smart Privacy protections designed into the system.

MitigationUpdate to the patched version of the Apple/Google Exposure Notification API (post-2020-05-29) and ensure mobile OS versions support the corrected implementation. Review any custom implementations that may have replicated the vulnerable beta behavior.

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
The Rolling Proximity IdentifierApplication
Affected:<= 2020-05-29

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

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. Identify if your app implements Exposure Notification
    Review your mobile application's codebase and dependencies to determine if it integrates the Apple/Google Exposure Notification API (also known as GAEN or EN API). Check for imports of frameworks such as ExposureNotification in iOS or the COVID-19 Exposure Notifications system in Android.
    Affected if Your application integrates the Apple/Google Exposure Notification API for contact tracing functionality.
  2. Determine your Exposure Notification library version
    Check the version of the Exposure Notification SDK or framework bundled with your application. In iOS, inspect the ExposureNotification framework version. In Android, check the play-services-safetynet or exposure-notification library version in your build dependencies.
    Affected if The bundled library or framework version predates the 2020-05-29 patch.
  3. Verify your app build date
    Check the compilation or release date of your deployed mobile application binary. Examine the build metadata or the date when the app package (IPA/APK) was generated.
    Affected if The application was built or released prior to late May 2020, before the rolling proximity identifier fix was deployed.
  4. Check mobile OS version support
    Verify that the mobile operating system versions your app targets support the corrected Exposure Notification implementation. iOS should be version 13.5 or later; Android should have Google Play Services version 20.x or later that includes the patched EN API.
    Affected if Your app runs on or targets mobile OS versions that do not include the patched Exposure Notification system.
  5. Inspect for custom implementations
    If you developed a custom contact tracing implementation that replicates the Apple/Google API behavior, review your code to determine if it generates separate rotating and static identifiers. Check whether your implementation creates a secondary UID that remains constant while the primary proximity identifier rotates.
    Affected if Your custom implementation replicates the vulnerable beta behavior with a persistent static secondary UID.

Your environment is affected if your mobile application or custom implementation uses the Exposure Notification API or a replica thereof from before the 2020-05-29 patch, or runs on mobile OS versions that lack the patched API support.

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
Upgrade available Upgrade to a release after 2020-05-29
Vendor patch github.com →
Interim mitigation

Update to the patched version of the Apple/Google Exposure Notification API (post-2020-05-29) and ensure mobile OS versions support the corrected implementation. Review any custom implementations that may have replicated the vulnerable beta behavior.

Recommended fix Moderate confidence
  1. Navigate to the Google exposure-notifications-internals repository at github.com/google/exposure-notifications-internals
  2. Locate and review commit 8f751a666697 which addresses the secondary temporary UID vulnerability
  3. Analyze the code changes in the commit to understand the fix for the Rolling Proximity Identifier
  4. Apply the equivalent fix to your implementation of the Apple/Google Exposure Notification API
  5. Verify that the secondary temporary UID is no longer present in the rolling proximity identifier generation
  6. Test Bluetooth LE discovery to confirm devices can no longer be tracked via the secondary UID

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

Fix this in The Rolling Proximity Identifier Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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