The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsLearn about Use of a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.
Start learningUpgrade filezilla-client
to version 3.67.0 or higher.
Affected versions of this package are vulnerable to Use of a Broken or Risky Cryptographic Algorithm due to biased ECDSA nonce generation. An attacker can recover a user's NIST P-521 secret key via a quick attack in approximately 60 signatures. This vulnerability can only be exploited in scenarios where an adversary is able to read messages signed by the software or its agent. One scenario is that the adversary operates an SSH server to which the victim authenticates, 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. Here, the rogue server operator can derive the victim's private key, then use it for unauthorized access to those other services. This vulnerability could potentially be leveraged for supply-chain attacks on software maintained in Git.
Note:
The only affected key type is 521-bit ECDSA. That is, a key that appears in "Windows PuTTYgen" with ecdsa-sha2-nistp521
at the start of the 'Key fingerprint' box, or is described as 'NIST p521' when loaded into Windows Pageant, or has an id starting ecdsa-sha2-nistp521
in the SSH protocol or the key file. Other sizes of ECDSA, and other key algorithms, are unaffected. In particular, Ed25519
is not affected.