GitLab Runner

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

1. A command injection vulnerability was discovered in Gitlab runner versions prior to 13.2.4, 13.3.2 and 13.4.1. When the runner is configured on a Windows system with a docker exec…CVE-2020-13347GitLab · CVSS 9.1 · 2.3% likely

   CWE-22

2. Improper sanitization of branch names in GitLab Runner affecting all versions prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 allows a user who creates a branch wi…CVE-2022-2251GitLab · CVSS 4.8 · 1.2% likely

   CWE-78

3. For GitLab Runner before 13.0.12, 13.1.6, 13.2.3, by replacing dockerd with a malicious server, the Shared Runner is susceptible to SSRF.CVE-2020-13295GitLab · CVSS 5.4 · 1.2% likely

   CWE-918

4. An uncontrolled resource consumption vulnerability in GitLab Runner affecting all versions starting from 13.7 before 14.3.6, all versions starting from 14.4 before 14.4.4, all ver…CVE-2021-39939GitLab · CVSS 6.5 · 0.9% likely

   CWE-400

5. In specific circumstances, trace file buffers in GitLab Runner versions up to 14.3.4, 14.4 to 14.4.2, and 14.5 to 14.5.2 would re-use the file descriptor 0 for multiple traces and…CVE-2021-39947GitLab · CVSS 5.3 · 0.9% likely
6. An issue has been discovered in GitLab Runner affecting all versions starting from 13.4.0 before 13.4.2, all versions starting from 13.3.0 before 13.3.7, all versions starting fro…CVE-2020-13327GitLab · CVSS 6 · 0.7% likely

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.