File and Path Handling

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

1. Git clone remote code execution vulnerability in git-for-windowsCVE-2022-41953git-for-windows · CVSS 8.6 · 8.0% likely

   CWE-426

2. Uncontrolled search for the Git directory in Git for WindowsCVE-2022-24765git-for-windows · CVSS 6 · 1.0% likely

   CWE-427

3. Untrusted search path vulnerability in Git 1.x for Windows allows local users to gain privileges via a Trojan horse git.exe file in the current working directory. NOTE: 2.x is una…CVE-2016-9274Git For Windows Project · 0.9% likely

   CWE-426

4. Git looks for localized messages in the wrong placeCVE-2023-25815git-for-windows · CVSS 3.3 · 0.8% likely

   CWE-22

5. Git for Windows' installer can be tricked into executing an untrusted binaryCVE-2022-31012git-for-windows · CVSS 8.2 · 0.4% likely

   CWE-426

6. gitk can inadvertently call executables in the worktreeCVE-2023-23618git-for-windows · CVSS 8.6 · 0.4% likely

   CWE-426

7. Git for Windows's config file of `connect.exe` is susceptible to malicious placingCVE-2023-29011git-for-windows · CVSS 7.6 · 0.4% likely

   CWE-427

8. Git CMD erroneously executes `doskey.exe` in the current directory, if it existsCVE-2023-29012git-for-windows · CVSS 7.3 · 0.4% likely

   CWE-427

9. Git for Windows' installer is susceptible to DLL side loading attacksCVE-2023-22743git-for-windows · CVSS 7.3 · 0.4% likely

   CWE-426

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.