CVE-2020-13702
Apple Google Exposure Notification Bluetooth Smart Stealth Tracking Vulnerability
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.
INFO
Published Date :
June 11, 2020, 7:15 p.m.
Last Modified :
March 12, 2021, 12:58 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
5.8
Exploitability Score :
3.9
Affected Products
The following products are affected by CVE-2020-13702
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2020-13702.
| URL | Resource |
|---|---|
| https://blog.google/documents/70/Exposure_Notification_-_Bluetooth_Specification_v1.2.2.pdf | Third Party Advisory |
| https://github.com/google/exposure-notifications-internals/commit/8f751a666697 | Patch Third Party Advisory |
| https://github.com/google/exposure-notifications-internals/commit/8f751a666697c3cae0a56ae3464c2c6cbe31b69e | Patch Third Party Advisory |
| https://github.com/normanluhrmann/infosec/raw/master/exposure-notification-vulnerability-20200611.pdf | Exploit Technical Description Third Party Advisory |
| https://github.com/normanluhrmann/infosec/raw/master/exposure-notification-vulnerability-20200616-2.pdf | Exploit Technical Description Third Party Advisory |
| https://github.com/normanluhrmann/infosec/raw/master/exposure-notification-vulnerability-20200616.pdf | Exploit Technical Description Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2020-13702 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2020-13702 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Modified Analysis by [email protected]
Mar. 12, 2021
Action Type Old Value New Value Changed Reference Type https://github.com/google/exposure-notifications-internals/commit/8f751a666697 No Types Assigned https://github.com/google/exposure-notifications-internals/commit/8f751a666697 Patch, Third Party Advisory Changed Reference Type https://github.com/google/exposure-notifications-internals/commit/8f751a666697c3cae0a56ae3464c2c6cbe31b69e No Types Assigned https://github.com/google/exposure-notifications-internals/commit/8f751a666697c3cae0a56ae3464c2c6cbe31b69e Patch, Third Party Advisory -
CVE Modified by [email protected]
Mar. 01, 2021
Action Type Old Value New Value Changed Description ** DISPUTED ** 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. NOTE: this is disputed because the specification states "The advertiser address, Rolling Proximity Identifier, and Associated Encrypted Metadata shall be changed synchronously so that they cannot be linked" and therefore the purported tracking actually cannot occur. The original reporter says that synchronous changes only occur in one direction, not both directions. 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. Removed CVSS V3 MITRE AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N Added CVSS V3.1 MITRE AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Added Reference https://github.com/google/exposure-notifications-internals/commit/8f751a666697 [No Types Assigned] -
CVE Modified by [email protected]
Dec. 11, 2020
Action Type Old Value New Value Added Reference https://github.com/google/exposure-notifications-internals/commit/8f751a666697c3cae0a56ae3464c2c6cbe31b69e [No Types Assigned] -
Initial Analysis by [email protected]
Jun. 24, 2020
Action Type Old Value New Value Added CVSS V2 NIST (AV:N/AC:L/Au:N/C:P/I:P/A:N) Added CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N Changed Reference Type https://blog.google/documents/70/Exposure_Notification_-_Bluetooth_Specification_v1.2.2.pdf No Types Assigned https://blog.google/documents/70/Exposure_Notification_-_Bluetooth_Specification_v1.2.2.pdf Third Party Advisory Changed Reference Type https://github.com/normanluhrmann/infosec/raw/master/exposure-notification-vulnerability-20200611.pdf No Types Assigned https://github.com/normanluhrmann/infosec/raw/master/exposure-notification-vulnerability-20200611.pdf Exploit, Technical Description, Third Party Advisory Changed Reference Type https://github.com/normanluhrmann/infosec/raw/master/exposure-notification-vulnerability-20200616.pdf No Types Assigned https://github.com/normanluhrmann/infosec/raw/master/exposure-notification-vulnerability-20200616.pdf Exploit, Technical Description, Third Party Advisory Changed Reference Type https://github.com/normanluhrmann/infosec/raw/master/exposure-notification-vulnerability-20200616-2.pdf No Types Assigned https://github.com/normanluhrmann/infosec/raw/master/exposure-notification-vulnerability-20200616-2.pdf Exploit, Technical Description, Third Party Advisory Added CWE NIST CWE-200 Added CPE Configuration OR *cpe:2.3:a:the_rolling_proximity_identifier_project:the_rolling_proximity_identifier:*:*:*:*:*:*:*:* versions up to (including) 2020-05-29 -
CVE Modified by [email protected]
Jun. 16, 2020
Action Type Old Value New Value Changed Description ** DISPUTED ** 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. NOTE: this is disputed because the specification states "The advertiser address, Rolling Proximity Identifier, and Associated Encrypted Metadata shall be changed synchronously so that they cannot be linked" and therefore the purported tracking actually cannot occur. ** DISPUTED ** 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. NOTE: this is disputed because the specification states "The advertiser address, Rolling Proximity Identifier, and Associated Encrypted Metadata shall be changed synchronously so that they cannot be linked" and therefore the purported tracking actually cannot occur. The original reporter says that synchronous changes only occur in one direction, not both directions. Added Reference https://github.com/normanluhrmann/infosec/raw/master/exposure-notification-vulnerability-20200616-2.pdf [No Types Assigned] -
CVE Modified by [email protected]
Jun. 16, 2020
Action Type Old Value New Value Added Reference https://github.com/normanluhrmann/infosec/raw/master/exposure-notification-vulnerability-20200616.pdf [No Types Assigned] -
CVE Modified by [email protected]
Jun. 12, 2020
Action Type Old Value New Value Changed 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. ** DISPUTED ** 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. NOTE: this is disputed because the specification states "The advertiser address, Rolling Proximity Identifier, and Associated Encrypted Metadata shall be changed synchronously so that they cannot be linked" and therefore the purported tracking actually cannot occur. Added Reference https://blog.google/documents/70/Exposure_Notification_-_Bluetooth_Specification_v1.2.2.pdf [No Types Assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2020-13702 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2020-13702
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.36 }} 0.04%
score
0.72192
percentile