Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2024-31497: 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 qui

Noroxi assessment

Priority: Monitor (action score 25/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 5.7% (FIRST EPSS); higher than 93% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: putty (Alpine:v3.16) 0.81-r0; putty (Debian:10) 0.74-1+deb11u1~deb10u2; putty (Debian:12) 0.78-2+deb12u2.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to putty (Alpine:v3.16) 0.81-r0; putty (Debian:10) 0.74-1+deb11u1~deb10u2; putty (Debian:12) 0.78-2+deb12u2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.9 · v3.1—Proof of concept Fix available
Published
Apr 15, 2024
Updated
Jun 17, 2026
EPSS
5.7% · 93th percentile

Report tools

JSON

Action score

25

Monitor

Low priority for now.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 5.7%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-31497

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
puttyputty
filezilla-projectfilezilla client
winscpwinscp
tortoisegittortoisegit
tigristortoisesvn
fedoraprojectfedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject fedora38
  • fedoraproject fedora39
  • fedoraproject fedora40
  • filezilla-project filezilla clientbefore 3.67.0
  • putty putty0.68 and later · before 0.81
  • tigris tortoisesvnbefore 1.14.6
  • tortoisegit tortoisegitbefore 2.15.0.1
  • winscp winscpbefore 6.3.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.16puttyfrom 0.68 · before 0.81-r00.81-r0
Debian:10puttybefore 0.74-1+deb11u1~deb10u20.74-1+deb11u1~deb10u2
Debian:12filezillafrom 0—
Debian:12puttybefore 0.78-2+deb12u20.78-2+deb12u2
Debian:13filezillabefore 3.67.0-13.67.0-1
Debian:13puttybefore 0.81-10.81-1
openSUSE:Leap 15.5puttybefore 0.81-bp155.2.6.10.81-bp155.2.6.1
openSUSE:Tumbleweedfilezillabefore 3.67.0-1.13.67.0-1.1
openSUSE:Tumbleweedputtybefore 0.81-1.10.81-1.1
SUSE:Package Hub 15 SP5puttybefore 0.81-bp155.2.6.10.81-bp155.2.6.1

Other highest-scoring records for the same primary product.

  • CVE-2017-6542The ssh_agent_channel_data function in PuTTY before 0.68 allows remote attackers to have unspecified impact via a large length value in an a
    46Plan
  • CVE-2004-1008Integer signedness error in the ssh2_rdpkt function in PuTTY before 0.56 allows remote attackers to execute arbitrary code via a SSH2_MSG_DE
    42Plan
  • CVE-2019-9898Potential recycling of random numbers used in cryptography exists within PuTTY before 0.71.
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2021-33500May 21, 2021 · PuTTY before 0.75 on Windows allows remote servers to cause a denial of service (Windows GUI hang) by telling the PuTTY window to change its
    31Monitor
  • ← EarlierCVE-2021-36367Jul 9, 2021 · PuTTY through 0.75 proceeds with establishing an SSH session even if it has never sent a substantive authentication response.
    32Monitor
  • Later →CVE-2026-4115Mar 22, 2026 · PuTTY Ed25519 Signature ecc-ssh.c eddsa_verify signature verification
    11Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:putty0.81-r0 · Alpine:v3.16Package registry (OSV)
debian:filezilla3.67.0-1 · Debian:13Package registry (OSV)
debian:putty0.78-2+deb12u2 · Debian:12Package registry (OSV)
opensuse:filezilla3.67.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:putty0.81-bp155.2.6.1 · openSUSE:Leap 15.5Package registry (OSV)
suse:putty0.81-bp155.2.6.1 · SUSE:Package Hub 15 SP5Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×4

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02024-04-17
Proof-of-concept repository on GitHubstars:22024-04-17
Proof-of-concept repository on GitHubstars:112024-05-10
Proof-of-concept repository on GitHubstars:02025-10-16

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+1 d
  3. TodayOct 30, 2026+927 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (19 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records