Docker

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

1. runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leverag…CVE-2019-5736Docker · 98% likely

   CWE-78

2. In Docker 19.03.x before 19.03.1 linked against the GNU C Library (aka glibc), code injection can occur when the nsswitch facility dynamically loads a library inside a chroot that…CVE-2019-14271Docker · 19% likely

   CWE-665

3. Docker 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted (1) image or (2) build in a Dockerfile in an LZMA (.xz) archive, related to the c…CVE-2014-9357Docker · 6.2% likely

   CWE-264

4. Path traversal vulnerability in Docker before 1.3.3 allows remote attackers to write to arbitrary files and bypass a container protection mechanism via a full pathname in a symlin…CVE-2014-9356Docker · 4.9% likely

   CWE-22

5. Docker before 1.3.2 allows remote attackers to write to arbitrary files and execute arbitrary code via a (1) symlink or (2) hard link attack in an image archive in a (a) pull or (…CVE-2014-6407Docker · 4.9% likely

   CWE-59

6. runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because libcontainer/rootfs_linux.go incorrectly checks mount t…CVE-2019-16884Docker · 4.4% likely

   CWE-863

7. In Docker CE and EE before 18.09.8 (as well as Docker EE before 17.06.2-ee-23 and 18.x before 18.03.1-ee-10), Docker Engine in debug mode may sometimes add secrets to the debug lo…CVE-2019-13509Docker · 3.7% likely

   CWE-532

8. In Docker through 18.06.1-ce-rc2, the API endpoints behind the 'docker cp' command are vulnerable to a symlink-exchange attack with Directory Traversal, giving attackers arbitrary…CVE-2018-15664Docker · 3.4% likely

   CWE-362

9. Docker 1.3.0 through 1.3.1 allows remote attackers to modify the default run profile of image containers and possibly bypass the container by applying unspecified security options…CVE-2014-6408Docker · 3.1% likely

   CWE-264

10. The SwarmKit toolkit 1.12.0 for Docker allows remote authenticated users to cause a denial of service (prevention of cluster joins) via a long sequence of join and quit actions. N…CVE-2016-6595Docker · 2.8% likely

    CWE-399

11. Docker Engine 1.12.2 enabled ambient capabilities with misconfigured capability policies. This allowed malicious images to bypass user permissions to access files within the conta…CVE-2016-8867Docker · 2.8% likely

    CWE-264

12. Docker before 1.3.3 does not properly validate image IDs, which allows remote attackers to conduct path traversal attacks and spoof repositories via a crafted image in a (1) "dock…CVE-2014-9358Docker · 2.5% likely

    CWE-20

13. Lack of content verification in Docker-CE (Also known as Moby) versions 1.12.6-0, 1.10.3, 17.03.0, 17.03.1, 17.03.2, 17.06.0, 17.06.1, 17.06.2, 17.09.0, and earlier allows a remot…CVE-2017-14992Docker · 2.5% likely

    CWE-20

14. HandleRequestAsync in Docker for Windows before 18.06.0-ce-rc3-win68 (edge) and before 18.06.0-ce-win72 (stable) deserialized requests over the \\.\pipe\dockerBackend named pipe w…CVE-2018-15514Docker · 2.4% likely

    CWE-502

15. In Docker before 18.09.4, an attacker who is capable of supplying or manipulating the build path for the "docker build" command would be able to gain command execution. An issue e…CVE-2019-13139Docker · 2.0% likely

    CWE-78

16. Docker before 1.3.1 and docker-py before 0.5.3 fall back to HTTP when the HTTPS connection to the registry fails, which allows man-in-the-middle attackers to conduct downgrade att…CVE-2014-5277Docker · 1.9% likely

    CWE-17

17. util/binfmt_misc/check.go in Builder in Docker Engine before 19.03.9 calls os.OpenFile with a potentially unsafe qemu-check temporary pathname, constructed with an empty first arg…CVE-2020-27534Docker · 1.8% likely

    CWE-22

18. A vulnerability exists in Docker before 1.2 via container names, which may collide with and override container IDs.CVE-2014-5278Docker · 1.5% likely
19. Docker before 1.3 does not properly validate image IDs, which allows remote attackers to redirect to another image through the loading of untrusted images via 'docker load'.CVE-2014-5282Docker · 1.3% likely

    CWE-20

20. The default OCI linux spec in oci/defaults{_linux}.go in Docker/Moby from 1.11 to current does not block /proc/acpi pathnames. The flaw allows an attacker to modify host's hardwar…CVE-2018-10892Docker · CVSS 6.3 · 1.1% likely

    CWE-250

21. Docker Desktop before 4.5.1 on Windows allows attackers to move arbitrary files. NOTE: this issue exists because of an incomplete fix for CVE-2022-23774.CVE-2022-25365Docker · CVSS 7.8 · 0.8% likely
22. Libcontainer and Docker Engine before 1.6.1 opens the file-descriptor passed to the pid-1 process before performing the chroot, which allows local users to gain privileges via a s…CVE-2015-3627Docker · 0.6% likely

    CWE-59

23. Docker Engine before 1.6.1 allows local users to set arbitrary Linux Security Modules (LSM) and docker_t policies via an image that allows volumes to override files in /proc.CVE-2015-3631Docker · 0.6% likely

    CWE-264

24. Docker Engine before 1.6.1 uses weak permissions for (1) /proc/asound, (2) /proc/timer_stats, (3) /proc/latency_stats, and (4) /proc/fs, which allows local users to modify the hos…CVE-2015-3630Docker · 0.5% likely

    CWE-264

25. RunC allowed additional container processes via 'runc exec' to be ptraced by the pid 1 of the container. This allows the main processes of the container, if running as root, to ga…CVE-2016-9962Docker · 0.4% likely

    CWE-362

26. Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors.CVE-2014-3499Docker · 0.4% likely

    CWE-264

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.