Use of a Broken or Risky Cryptographic Algorithm Affecting libssh package, versions [,0.11.2)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
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.
Do your applications use this vulnerable package?
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 applicationsSnyk Learn
Learn about Use of a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-UNMANAGED-LIBSSH-10753748
- published16 Jul 2025
- disclosed24 Jun 2025
- creditRonald Crane
Introduced: 24 Jun 2025
NewCVE-2025-5372 (opens in a new tab)How to fix?
Upgrade libssh to version 0.11.2 or higher.
Overview
Affected versions of this package are vulnerable to Use of a Broken or Risky Cryptographic Algorithm via the ssh_kdf() function when built with OpenSSL versions older than 3.0. An attacker can compromise the confidentiality, integrity, and availability of SSH sessions by triggering cryptographic operations that use uninitialized key material.
Workaround
This vulnerability can be mitigated by building the library against OpenSSL version 3.0 or later.