CVE-2024-31497
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 · uneditedIn 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.
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 analysisA detailed technical summary for this CVE is being prepared.
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= 38= 39= 40>= 0.68, < 0.81< 3.67.0< 6.3.3< 2.15.0.1< 1.14.6CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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.811.14.62.15.0.1
PuTTY 0.81; FileZilla 3.67.0; WinSCP 6.3.3; TortoiseGit 2.15.0.1; TortoiseSVN 1.14.6; Fedora latest security updates
- 1. Identify all affected PuTTY-based products in use across your environment (PuTTY, Pageant, FileZilla, WinSCP, TortoiseGit, TortoiseSVN)
- 2. For PuTTY: Upgrade to version 0.81 or later from https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
- 3. For FileZilla Client: Upgrade to version 3.67.0 or later from https://filezilla-project.org/
- 4. For WinSCP: Upgrade to version 6.3.3 or later from https://winscp.net/eng/download.php
- 5. For TortoiseGit: Upgrade to version 2.15.0.1 or later from https://tortoisegit.org/
- 6. For TortoiseSVN: Upgrade to version 1.14.6 or later from https://tortoisesvn.net/downloads.html
- 7. For Fedora systems: Update system packages via 'dnf update' to receive security patches addressing this vulnerability
- 8. After upgrading, revoke and regenerate any ECDSA P-521 keys that were used with vulnerable versions, as they may be compromised
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31497 — 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 sources- git.tartarus.org
- www.chiark.greenend.org.uk
- www.chiark.greenend.org.uk
- git.tartarus.org
- www.openwall.com
- github.com
- github.com
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- security-tracker.debian.org
- tortoisegit.org
- winscp.net
- www.openwall.com
- docs.ccv.brown.edu
- filezilla-project.org
- tartarus.org
- bugzilla.redhat.com
- bugzilla.suse.com
- news.ycombinator.com
- lists.debian.org
- securityonline.info
- twitter.com
- twitter.com
- www.bleepingcomputer.com
- www.reddit.com
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- www.vicarius.io
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-31497 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