Approved changes feed: RSS · Atom

cpe:2.3:a:putty:putty:-:*:*:*:*:*:*:*

part: a version: - update: *

VendorPutty (008a1fed-a309-5584-beef-53a3aa2b274b)
ProductPutty (6ccb8ecc-45e0-571f-81e1-43f27834557c)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:deb/debian/putty purl2cpe 2026-06-01 10:15:26.540134
pkg:deb/ubuntu/putty purl2cpe 2026-06-01 10:15:26.540137
pkg:rpm/fedora/putty purl2cpe 2026-06-01 10:15:26.540140
pkg:rpm/opensuse/putty purl2cpe 2026-06-01 10:15:26.540143

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2024-31497 vulnerable 2026-06-08 06:35:31.939352 Details available
In PuTTY 0.68 through 0.80 before 0.81, biased ECDSA nonce generation allows an attacker to recover a user's NIST P-521 secret key via a quick attack in approximately 60 signatures. This is especially important in a scenario where an adversary is able to read messages signed by PuTTY or Pageant. The required set of signed messages may be publicly readable because they are stored in a public Git service that supports use of SSH for commit signing, and the signatures were made by Pageant through an agent-forwarding mechanism. In other words, an adversary may already have enough signature information to compromise a victim's private key, even if there is no further use of vulnerable PuTTY versions. After a key compromise, an adversary may be able to conduct supply-chain attacks on software maintained in Git. A second, independent scenario is that the adversary is an operator of an SSH server to which the victim authenticates (for remote login or file copy), even though this server is not fully trusted by the victim, and the victim uses the same private key for SSH connections to other services operated by other entities. Here, the rogue server operator (who would otherwise have no way to determine the victim's private key) can derive the victim's private key, and then use it for unauthorized access to those other services. If the other services include Git services, then again it may be possible to conduct supply-chain attacks on software maintained in Git. This also affects, for example, FileZilla before 3.67.0, WinSCP before 6.3.3, TortoiseGit before 2.15.0.1, and TortoiseSVN through 1.14.6.
Published: 2024-04-15T00:00:00.000Z
Updated: 2025-11-04T22:06:12.533Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-36367 vulnerable 2026-06-08 05:32:52.087030 Details available
PuTTY through 0.75 proceeds with establishing an SSH session even if it has never sent a substantive authentication response. This makes it easier for an attacker-controlled SSH server to present a later spoofed authentication prompt (that the attacker can use to capture credential data, and use that data for purposes that are undesired by the client user).
Published: 2021-07-09T00:00:00.000Z
Updated: 2024-08-04T00:54:51.472Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.