CVE-2019-17067
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 · uneditedPuTTY before 0.73 on Windows improperly opens port-forwarding listening sockets, which allows attackers to listen on the same port to steal an incoming connection.
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 · high confidencePuTTY versions prior to 0.73 on Windows improperly opens port-forwarding listening sockets, allowing multiple processes to bind to the same port. This enables a local attacker to intercept and steal incoming SSH port-forwarding connections by binding to the same port before the legitimate PuTTY session.
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< 0.73CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate PuTTY installation on WindowsSearch for putty.exe in common installation directories (C:\Program Files\PuTTY, C:\Program Files (x86)\PuTTY) or check Start Menu for PuTTY entries. Also check PATH directories.Affected if PuTTY is found on the Windows system
-
Identify PuTTY version numberRight-click putty.exe, select Properties, then go to the Details tab to view Product Version. Alternatively, run 'putty.exe --version' or 'putty.exe -V' from command prompt.Affected if Version is less than 0.73 (e.g., 0.72, 0.71, etc.)
-
Confirm Windows platformVerify the operating system is Windows. This vulnerability only affects Windows versions of PuTTY, not Linux or macOS.Affected if Running on Windows operating system
-
Check for active port forwarding sessionsReview PuTTY saved sessions or active connections that use SSH port forwarding (look for configured tunnels in saved session settings or check running PuTTY processes with -L or -R options).Affected if Port forwarding tunnels (-L local, -R remote, or -D dynamic) are configured or active
User is affected if PuTTY version is below 0.73 on Windows and port forwarding tunnels are being used, allowing a local attacker to bind to the same forwarding port.
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 · scoped0.73
Update PuTTY to version 0.73 or later on all Windows workstations. For organizations, deploy the patched version through existing software distribution mechanisms and verify completion.
PuTTY 0.73
- Download PuTTY version 0.73 or later from the official PuTTY website (https://www.chiark.greenend.org.uk/~sgtatham/putty/)
- Install the new version of PuTTY
- If you use PuTTY in shared environments, ensure all users upgrade to version 0.73 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17067 — 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-2019-17067 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