Information Disclosure

Every one of the 817 is a mark on the map. Named now: 1 to 26, most at risk first.

1. The Android browser in Android before 2.3.4 allows remote attackers to obtain SD card contents via crafted content:// URIs, related to (1) BrowserActivity.java and (2) BrowserSett…CVE-2010-4804Google · 27% likely

   CWE-200

2. A information disclosure vulnerability in the Android system (bluetooth). Product: Android. Versions: 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0. Android ID: A-631466…CVE-2017-0785Google Inc. · 12% likely

   CWE-200

3. The get_sos function in jdmarker.c in (1) libjpeg 6b and (2) libjpeg-turbo through 1.3.0, as used in Google Chrome before 31.0.1650.48, Ghostscript, and other products, does not c…CVE-2013-6629Google · 9.7% likely

   CWE-200

4. Inappropriate implementation in WebRTC in Google Chrome prior to 84.0.4147.89 allowed an attacker in a privileged network position to potentially exploit heap corruption via a cra…CVE-2020-6514Google · 7.8% likely

   CWE-200

5. uri.js in Google V8 before 5.1.281.26, as used in Google Chrome before 51.0.2704.63, uses an incorrect array type, which allows remote attackers to obtain sensitive information by…CVE-2016-1677Google · 3.1% likely

   CWE-200

6. Lack of CORS checking by ResourceFetcher/ResourceLoader in Blink in Google Chrome prior to 65.0.3325.146 allowed a remote attacker to leak cross-origin data via a crafted HTML pag…CVE-2018-6066Google · 2.8% likely

   CWE-200

7. The xsltGenerateIdFunction function in functions.c in libxslt 1.1.26 and earlier, as used in Google Chrome before 10.0.648.127 and other products, allows remote attackers to obtai…CVE-2011-1202Google · 2.5% likely

   CWE-200

8. In parseNextBox of IsoInterface.java, there is a possible leak of unredacted location information due to improper input validation. This could lead to remote information disclosur…CVE-2021-0340Google · 2.2% likely

   CWE-212

9. Google Chrome before 18.0.1025308 on Android allows remote attackers to obtain cookie information via a crafted application.CVE-2012-4909Google · 2.1% likely

   CWE-200

10. The Content Security Policy (CSP) implementation in Blink, as used in Google Chrome before 49.0.2623.75, does not ignore a URL's path component in the case of a ServiceWorker fetc…CVE-2016-2845Google · 2.1% likely

    CWE-200

11. Inappropriate implementation in CORS in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to leak cross-origin data via a crafted HTML page.CVE-2020-6400Google · 2.0% likely

    CWE-203

12. Binder in the kernel in Android before 2016-10-05 on Nexus devices allows attackers to obtain sensitive information via a crafted application, aka internal bug 30768347.CVE-2016-6689Google · 2.0% likely

    CWE-200

13. Confusing settings in Autofill in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML…CVE-2018-6117Google · 1.9% likely

    CWE-200

14. CSS Paint API in Blink in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to leak cross-origin data via a crafted HTML page.CVE-2018-6137Google · 1.9% likely

    CWE-200

15. The Web Workers implementation in Google Chrome before 10.0.648.127 allows remote attackers to bypass the Same Origin Policy via unspecified vectors, related to an "error message…CVE-2011-1190Google · 1.9% likely

    CWE-200

16. Insufficient origin checks for CSS content in Blink in Google Chrome prior to 68.0.3440.75 allowed a remote attacker to leak cross-origin data via a crafted HTML page.CVE-2018-6164Google · 1.9% likely

    CWE-200

17. The parser in Google V8, as used in Google Chrome before 53.0.2785.113, mishandles scopes, which allows remote attackers to obtain sensitive information from arbitrary memory loca…CVE-2016-5172Google · 1.9% likely

    CWE-200

18. Unsafe handling of credit card details in Autofill in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to obtain potentially sensitive information from process memory…CVE-2018-16078Google · 1.8% likely

    CWE-200

19. Insufficient policy enforcement in Blink in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to obtain potentially sensitive information from process memory via a cra…CVE-2020-6473Google · 1.8% likely

    CWE-203

20. Inappropriate sharing of TEXTURE_2D_ARRAY/TEXTURE_3D data between tabs in WebGL in Google Chrome prior to 65.0.3325.146 allowed a remote attacker to leak cross-origin data via a c…CVE-2018-6079Google · 1.7% likely

    CWE-200

21. Use of an uninitialized value in Skia in Google Chrome prior to 61.0.3163.79 for Linux and Windows allowed a remote attacker to obtain potentially sensitive information from proce…CVE-2017-5117Google · 1.7% likely

    CWE-200

22. An information disclosure vulnerability in kernel components including the ION subsystem, Binder, USB driver and networking subsystem could enable a local malicious application to…CVE-2016-8405Google Inc. · 1.7% likely

    CWE-200

23. Information leak in content security policy in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to leak cross-origin data via a crafted HTML page.CVE-2020-6511Google · 1.7% likely

    CWE-209

24. An information disclosure vulnerability in the Qualcomm bootloader could help to enable a local malicious application to to execute arbitrary code within the context of the bootlo…CVE-2017-0455Google Inc. · 1.7% likely

    CWE-200

25. Google Chrome before 10.0.648.127 allows remote attackers to bypass the Same Origin Policy via unspecified vectors, related to an "error message leak."CVE-2011-1187Google · 1.7% likely

    CWE-200

26. A timing attack in SVG rendering in Google Chrome prior to 60.0.3112.78 for Linux, Windows, and Mac allowed a remote attacker to extract pixel values from a cross-origin page bein…CVE-2017-5107Google · 1.7% likely

    CWE-203

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.