CVE-2023-23618
About
Git for Windows is the Windows port of the revision control system Git. Prior to Git for Windows version 2.39.2, when `gitk` is run on Windows, it potentially runs executables from the current directory inadvertently, which can be exploited with some social engineering to trick users into running untrusted code. A patch is available in version 2.39.2. As a workaround, avoid using `gitk` (or Git GUI's "Visualize History" functionality) in clones of untrusted repositories.
Rainforest analyst review
When gitk runs on Git for Windows before 2.39.2, it can inadvertently execute programs from the current working directory. Clone a hostile repository, open it with gitk (or Git GUI's Visualize History), and a planted executable in that directory can run, courtesy of Windows' search-path behavior. The vector is local and requires the user to take those steps, but the result is untrusted code execution on a developer's machine.
This is a social-engineering play against developers specifically: the attacker's work is getting someone to clone a malicious repo and then use gitk on it, which is plausible in a world of casual git clones from unfamiliar sources but is still a real gate, not a drive-by. The scope-changed, high-impact metrics reflect that once it fires it can fully compromise the user context; the tempo is bounded by the need for that human step.
Our angle is developer-endpoint hygiene and proportionality. We would push the Git for Windows update to 2.39.2 across engineering machines and reinforce the workaround, avoid gitk on untrusted clones, since the precondition is entirely about developer behavior. We rank it as a meaningful workstation risk rather than an infrastructure emergency, because it can't be triggered without a user cloning and inspecting attacker-controlled code.
References
Related CVEs
No related CVEs.
Frequently asked questions
What is CVE-2023-23618?
Git for Windows is the Windows port of the revision control system Git. Prior to Git for Windows version 2.39.2, when `gitk` is run on Windows, it potentially runs executables from the current directory inadvertently, which can be exploited with some social engineering to trick users into running untrusted code. A patch is available in version 2.39.2.
How severe is CVE-2023-23618?
CVE-2023-23618 carries a CVSS 3.1 base score of 8.6, rated high. On the Rainforest Risk Index — which weighs the severity alongside how easy the flaw is to reach and how broad its impact is — it scores 81 out of 100, in the high band.
How is CVE-2023-23618 exploited?
According to the CVSS vector (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H): attack vector Local, attack complexity Low, privileges required None, user interaction Required. Impact on confidentiality High, integrity High and availability High.
Which products are affected by CVE-2023-23618?
Public advisories list the following as affected: git for windows. Check the references on this page for the exact versions each vendor confirms.
How do I fix CVE-2023-23618?
Apply the fix the vendor published — the references on this page link to the primary advisories and patches. When patching can't happen right away, reduce the exposure of the affected component and watch it for exploitation attempts. Rainforest customers see this vulnerability correlated to their own assets and prioritized by real exposure, not by score alone.
Empower Your Security Strategy with Rainforest
Discover vulnerabilities early, prioritize critical threats, and protect what truly matters. Rainforest streamlines your security operations, saving you time and reducing costs, so you can focus on what drives your business forward.