dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2025-5372

HIGH · 8.8 CVSS v3.1 Published 2025-07-04
Fix available
A fix is available. Upgrade to 0.11.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A flaw was found in libssh versions built with OpenSSL versions older than 3.0, specifically in the ssh_kdf() function responsible for key derivation. Due to inconsistent interpretation of return values where OpenSSL uses 0 to indicate failure and libssh uses 0 for success—the function may mistakenly return a success status even when key derivation fails. This results in uninitialized cryptographic key buffers being used in subsequent communication, potentially compromising SSH sessions' confidentiality, integrity, and availability.

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 analysis · high confidence

A return value interpretation mismatch in libssh's ssh_kdf() function causes it to report success when OpenSSL key derivation actually fails. This occurs because OpenSSL uses 0 to indicate failure while libssh uses 0 for success, leading to uninitialized cryptographic keys being used in SSH sessions.

MitigationUpgrade OpenSSL to version 3.0 or newer when building libssh, or update libssh to correctly handle OpenSSL return values in the ssh_kdf() function.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Openshift Container PlatformApplication
Affected:= 4.0
Enterprise LinuxOperating system
Affected:= 6.0= 7.0= 8.0= 9.0= 10.0
LibsshApplication
Affected:< 0.11.2

CVSS 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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed libssh version
    Run 'rpm -q libssh' or check your package manager for the libssh package version
    Affected if The installed version is less than 0.11.2
  2. Determine if SSH service is active
    Check if the SSH daemon is running using 'systemctl status sshd' or 'systemctl status ssh'
    Affected if SSH service is active and libssh version is vulnerable
  3. Check OpenSSL version in use
    Run 'openssl version' to identify the OpenSSL version
    Affected if OpenSSL version is older than 3.0 (the mismatch occurs when OpenSSL returns 0 for failure, which libssh misinterprets as success)
  4. Verify Red Hat Enterprise Linux version
    Run 'cat /etc/redhat-release' to check the RHEL version
    Affected if Running RHEL 6.0, 7.0, 8.0, 9.0, or 10.0 with vulnerable libssh
  5. Check for libssh usage in applications
    Identify applications linking to libssh using 'ldd' or 'lsof' on ssh-related binaries
    Affected if Applications use libssh for SSH key derivation and the library version is vulnerable

You are affected if libssh version is below 0.11.2 and SSH sessions are established using libssh, particularly when built against OpenSSL versions older than 3.0.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.11.2 or later
Fixed in 0.11.2
Interim mitigation

Upgrade OpenSSL to version 3.0 or newer when building libssh, or update libssh to correctly handle OpenSSL return values in the ssh_kdf() function.

Recommended fix Moderate confidence

libssh >= 0.11.2

  1. Identify the libssh package version currently installed using 'rpm -q libssh' or 'yum list installed libssh'
  2. For Red Hat Enterprise Linux systems, update via 'yum update libssh' or 'dnf update libssh' to pull the latest fixed package
  3. For OpenShift Container Platform 4.0, apply the corresponding security errata via 'oc adm upgrade' or through the web console
  4. Verify the updated version is 0.11.2 or later using 'rpm -q libssh'
  5. Restart any SSH services or containers using libssh to ensure the updated library is loaded
Caveat Ensure compatibility with dependent applications after library update; some legacy SSH configurations may need verification

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openshift Container Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5372 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5372 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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