dbcve.org
PuttyApplication

CVE-2019-17069

HIGH · 7.5 CVSS v3.1 Published 2019-10-01
Fix available
A fix is available. Upgrade to 0.73 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
PuTTY before 0.73 might allow remote SSH-1 servers to cause a denial of service by accessing freed memory locations via an SSH1_MSG_DISCONNECT message.

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 confidence

PuTTY before 0.73 contains a use-after-free vulnerability in its SSH-1 protocol implementation. A malicious remote SSH-1 server can send a specially crafted SSH1_MSG_DISCONNECT message that causes the client to access freed memory locations, resulting in a denial of service (crash).

MitigationUpgrade PuTTY to version 0.73 or later, which contains the fix for this vulnerability.

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
PuttyApplication
Affected:< 0.73
LeapOperating system
Affected:= 15.0= 15.1
Oncommand Unified Manager Core PackageApplication
Affected:all versions

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check PuTTY version number
    Run 'putty --version' from command line, or open PuTTY and go to Help > About to view the version
    Affected if Version is lower than 0.73 (e.g., 0.72, 0.71, etc.)
  2. Verify if SSH-1 protocol is enabled or has been used
    Check PuTTY configuration under Connection > SSH and look for 'SSH protocol version' setting, or review saved session configurations for any that use SSH-1
    Affected if SSH-1 protocol is selected or any saved sessions use SSH-1 (protocol version 1)
  3. Check OpenSUSE putty package version (OpenSUSE systems only)
    Run 'rpm -q putty' or 'zypper info putty' to retrieve the installed package version
    Affected if Running OpenSUSE Leap 15.0 or 15.1 with putty package installed (all versions of putty on these OS versions are affected)
  4. Confirm NetApp Oncommand Unified Manager installation (NetApp systems only)
    Run 'rpm -q Oncommand-Unified-Manager' or check for installation directory /opt/netapp/ocum/
    Affected if Oncommand Unified Manager Core Package is installed (all versions are affected per vendor advisory)

You are affected if you run any PuTTY version below 0.73 AND have SSH-1 protocol enabled or used, or if running affected OpenSUSE Leap 15.0/15.1 with putty, or any NetApp Oncommand Unified Manager version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 0.73 or later
Fixed in 0.73
Interim mitigation

Upgrade PuTTY to version 0.73 or later, which contains the fix for this vulnerability.

Fix this in Putty Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-17069 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-17069 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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