CVE-2024-45301
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMintty is a terminal emulator for Cygwin, MSYS, and WSL. In versions 2.3.6 through 3.7.4, several escape sequences can cause the mintty process to access a file in a specific path. It is triggered by simply printing them out on bash. An attacker can specify an arbitrary network path, negotiate an ntlm hash out of the victim's machine to an attacker controlled remote host. An attacker can use password cracking tools or NetNTLMv2 hashes to Pass the Hash. Version 3.7.5 fixes the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn mintty versions 2.3.6 through 3.7.4, specific escape sequences printed to the terminal cause the application to access arbitrary file paths, including network paths. This can trigger NTLM authentication negotiation to attacker-controlled remote hosts, allowing capture of NetNTLMv2 hashes for offline cracking or pass-the-hash attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify mintty is installedRun 'mintty --version' in a command prompt or check for mintty.exe in common installation paths such as C:\msys64\usr\bin\mintty.exe, C:\Program Files\Git\usr\bin\mintty.exe, or C:\Program Files (x86)\mintty\mintty.exeAffected if mintty executable is found on the system
-
Retrieve the installed version numberExecute 'mintty --version' and note the version string displayed (format typically shows version like 3.x.x or 2.x.x)Affected if version command fails or returns no output, indicating mintty may not be properly installed
-
Compare version against affected rangeParse the version number from the previous step and check if it falls within the range 2.3.6 through 3.7.4 (inclusive)Affected if version is 2.3.6, 2.3.7, 2.3.8, 2.3.9, 2.3.10, 3.0.0 through 3.7.4, or any version between these bounds
User is affected if mintty version is 2.3.6, 2.3.7, 2.3.8, 2.3.9, 2.3.10, or any version from 3.0.0 through 3.7.4 inclusive.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade mintty to version 3.7.5 or later to resolve the vulnerability.
Version 3.7.5 or later
- Identify the mintty installation source (Cygwin, MSYS2, or WSL)
- For Cygwin users: Run the Cygwin setup installer, search for mintty package, and update to version 3.7.5 or later
- For MSYS2 users: Open MSYS2 terminal and run 'pacman -Syu mintty' to update to the latest version
- For WSL users: Update via the underlying Linux distribution's package manager (e.g., 'sudo apt update && sudo apt upgrade' for Debian/Ubuntu-based WSL)
- Verify the installed version by running 'mintty --version' or checking the installed package version
- Restart any running mintty terminals to ensure the updated version is in use
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45301 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45301 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data