dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2025-5318

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-24
Fix available
A fix is available. Upgrade to 0.11.2 or later.
See remediation →
60/100
Remediation priority · Elevated
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 the libssh library in versions less than 0.11.2. An out-of-bounds read can be triggered in the sftp_handle function due to an incorrect comparison check that permits the function to access memory beyond the valid handle list and to return an invalid pointer, which is used in further processing. This vulnerability allows an authenticated remote attacker to potentially read unintended memory regions, exposing sensitive information or affect service behavior.

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 flaw in libssh versions before 0.11.2 allows an out-of-bounds read in the sftp_handle function due to an incorrect comparison check. This permits access to memory beyond the valid handle list, returning an invalid pointer that can expose sensitive memory contents to authenticated remote attackers.

MitigationUpgrade libssh to version 0.11.2 or later to resolve the incorrect comparison check in the sftp_handle 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:= 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
Low
Integrity
Low
Availability
None

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

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 library version
    Run 'rpm -q libssh' (RHEL) or check via package manager. For systems with the library directly, run 'ssh -V' or check /usr/lib/libssh.so.* version. Also check 'ldd <application>' to find which applications link to libssh.
    Affected if The installed libssh version is lower than 0.11.2, or the version cannot be determined and the product matches RHEL 8.0, 9.0, 10.0 or OpenShift Container Platform 4.0
  2. Confirm SFTP functionality is in use
    Check if the system runs any SFTP server or client services. Look for sftp-server in /usr/libexec/, check SSH daemon config for 'Subsystem sftp' in /etc/ssh/sshd_config, or review application logs for sftp-handle activity.
    Affected if SFTP subsystem or any application using libssh SFTP functions is enabled or running
  3. Verify authentication mechanisms
    Review SSH daemon configuration (/etc/ssh/sshd_config) to confirm password-based or public-key authentication is enabled for remote users, as the attacker needs valid credentials.
    Affected if Remote user authentication is permitted (not restricted to key-based only with additional MFA)
  4. Check for exposed SSH/SFTP services
    Scan network for open port 22 (SSH) or review firewall rules. Identify if SFTP services are exposed externally or to untrusted networks using 'nmap -sV -p 22 <target>' or 'netstat -tlnp | grep ssh'.
    Affected if SFTP service is accessible from network segments beyond trusted administrators

You are affected if libssh version is below 0.11.2 AND SFTP functionality is enabled and accessible with authenticated remote access.

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 libssh to version 0.11.2 or later to resolve the incorrect comparison check in the sftp_handle function.

Recommended fix High confidence

libssh 0.11.2

  1. Identify all systems with libssh versions lower than 0.11.2
  2. Update the libssh package to version 0.11.2 or later using the system package manager (e.g., dnf update libssh or yum update libssh)
  3. After updating libssh, restart any services that depend on it (such as sshd, sftp servers, or applications using libssh)
  4. Verify the installed libssh version is 0.11.2 or newer using: rpm -q libssh
Caveat Minor: SSH services utilizing libssh should be restarted after the update to load the fixed library

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

Fix this in Openshift Container Platform Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5318 — 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-5318 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