<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-09T17:49:14.361999+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cnvd-2020-51563</id>
    <title>cnvd-2020-51563</title>
    <updated>2026-11-09T17:49:14.366139+00:00</updated>
    <content>cnvd-2020-51563</content>
    <link href="https://db.gcve.eu/vuln/cnvd-2020-51563"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2020-13702</id>
    <title>fkie_cve-2020-13702</title>
    <updated>2026-11-09T17:49:14.366204+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2020-13702"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-49fh-5689-5m82</id>
    <title>GHSA-49fh-5689-5m82</title>
    <updated>2026-11-09T17:49:14.366245+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-49fh-5689-5m82"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/gsd-2020-13702</id>
    <title>gsd-2020-13702</title>
    <updated>2026-11-09T17:49:14.366263+00:00</updated>
    <content>gsd-2020-13702</content>
    <link href="https://db.gcve.eu/vuln/gsd-2020-13702"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/var-202006-0176</id>
    <title>VAR-202006-0176</title>
    <updated>2026-11-09T17:49:14.366274+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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. ** Unsettled ** This case has not been confirmed as a vulnerability. The Rolling Proximity Identifier There is an information leakage vulnerability in. Vendors have challenged this vulnerability. For more information, please see below NVD of Current Description Please Confirm. https://nvd.nist.gov/vuln/detail/CVE-2020-13702Information may be obtained</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/var-202006-0176"/>
  </entry>
</feed>
