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.

The remote Fedora 40 host has packages installed that are affected by a vulnerability as referenced in the FEDORA-2024-ff9a2fb31c advisory.

  - 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. (CVE-2024-31497)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Fedora 39 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2024-cba85cc558 advisory.

  - 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. (CVE-2024-31497)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 38 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2024-08a4a5ead8 advisory.

  - 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. (CVE-2024-31497)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 38 host has packages installed that are affected by a vulnerability as referenced in the FEDORA-2024-0489e7ba1e advisory.

  - 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. (CVE-2024-31497)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote openSUSE 15 host has a package installed that is affected by a vulnerability as referenced in the openSUSE- SU-2024:0111-1 advisory.

  - 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. (CVE-2024-31497)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Fedora 39 host has packages installed that are affected by a vulnerability as referenced in the FEDORA-2024-8401d42de6 advisory.

  - 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. (CVE-2024-31497)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

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. 

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the 080936ba-fbb7-11ee-abc8-6960f2492b1d advisory.

  - 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. (CVE-2024-31497)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
194522	Fedora 40 : filezilla / libfilezilla (2024-ff9a2fb31c)	Nessus	Fedora Local Security Checks	medium
193907	Fedora 39 : putty (2024-cba85cc558)	Nessus	Fedora Local Security Checks	medium
193903	Fedora 38 : putty (2024-08a4a5ead8)	Nessus	Fedora Local Security Checks	medium
193865	Fedora 38 : filezilla / libfilezilla (2024-0489e7ba1e)	Nessus	Fedora Local Security Checks	medium
193806	openSUSE 15 Security Update : putty (openSUSE-SU-2024:0111-1)	Nessus	SuSE Local Security Checks	medium
193455	Fedora 39 : filezilla / libfilezilla (2024-8401d42de6)	Nessus	Fedora Local Security Checks	medium
193433	PuTTY < 0.81 Key Recovery Attack Vulnerability	Nessus	Windows	high
193367	FreeBSD : PuTTY and embedders (f.i., filezilla) -- biased RNG with NIST P521/ecdsa-sha2-nistp521 signatures permits recovering private key (080936ba-fbb7-11ee-abc8-6960f2492b1d)	Nessus	FreeBSD Local Security Checks	medium

Detections

Analytics

CVE-2024-31497

medium

Tenable Plugins

medium

medium

medium

medium

medium

medium

high

medium