CVE-2021-31701
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 before 3.4.7 mishandles Bracketed Paste Mode.
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 confidenceMintty (a terminal emulator for Cygwin/MSYS2) before version 3.4.7 contains a vulnerability in its handling of Bracketed Paste Mode, a terminal feature that uses escape sequences to distinguish pasted text from typed input. The exact nature of the mishandling is not specified in the available description, but the CVSS 7.5 score indicates a significant security impact.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.4.7CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Check installed Mintty versionRun 'mintty --version' in a Mintty terminal, or right-click the Mintty window title and select 'About' to view the version numberAffected if The version displayed is lower than 3.4.7 (for example, 3.4.6, 3.4.0, 3.3.0, etc.)
-
Verify Bracketed Paste Mode statusIn the Mintty terminal, run the command 'printf "\033[?2004h"; echo "BPM enabled"' to enable Bracketed Paste Mode, then test pasting text. Alternatively, check if options for paste mode are enabled in Mintty settings (Options > Paste).Affected if Bracketed Paste Mode is enabled or can be activated, since the vulnerability exists in how Mintty handles this mode.
-
Confirm environment typeVerify that the terminal in use is Mintty (check the window title or process name). Mintty is commonly used with Cygwin and MSYS2 distributions.Affected if The terminal is Mintty running on Cygwin or MSYS2, and the version is below 3.4.7.
You are affected if you are running any version of Mintty earlier than 3.4.7 and Bracketed Paste Mode is enabled or may be triggered in your terminal sessions.
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.
From vendor data3.4.7
Upgrade Mintty to version 3.4.7 or later. Bracketed Paste Mode should be reviewed and tested after the upgrade to ensure proper functionality.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-31701 — 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-2021-31701 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