OESA-2025-2131 (CVE-2025-5987)
Vulnerability from osv_openeuler – Published: 2025-09-05 11:09 – Updated: 2026-08-06 11:09 – Source websiteThe ssh library was designed to be used by programmers needing a working SSH implementation by the mean of a library. The complete control of the client is made by the programmer. With libssh, you can remotely execute programs, transfer files, use a secure and transparent tunnel for your remote programs. With its Secure FTP implementation, you can play with remote files easily, without third-party programs others than libcrypto (from openssl).
Security Fix(es):
A flaw was found in libssh when using the ChaCha20 cipher with the OpenSSL library. If an attacker manages to exhaust the heap space, this error is not detected and may lead to libssh using a partially initialized cipher context. This occurs because the OpenSSL error code returned aliases with the SSH_OK code, resulting in libssh not properly detecting the error returned by the OpenSSL library. This issue can lead to undefined behavior, including compromised data confidentiality and integrity or crashes.(CVE-2025-5987)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"libssh-0.10.5-5.oe2403.aarch64.rpm",
"libssh-debuginfo-0.10.5-5.oe2403.aarch64.rpm",
"libssh-debugsource-0.10.5-5.oe2403.aarch64.rpm",
"libssh-devel-0.10.5-5.oe2403.aarch64.rpm"
],
"noarch": [
"libssh-help-0.10.5-5.oe2403.noarch.rpm"
],
"src": [
"libssh-0.10.5-5.oe2403.src.rpm"
],
"x86_64": [
"libssh-0.10.5-5.oe2403.x86_64.rpm",
"libssh-debuginfo-0.10.5-5.oe2403.x86_64.rpm",
"libssh-debugsource-0.10.5-5.oe2403.x86_64.rpm",
"libssh-devel-0.10.5-5.oe2403.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS",
"name": "libssh",
"purl": "pkg:rpm/openEuler/libssh\u0026distro=openEuler-24.03-LTS"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.10.5-5.oe2403"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The ssh library was designed to be used by programmers needing a working SSH\nimplementation by the mean of a library. The complete control of the client is\nmade by the programmer. With libssh, you can remotely execute programs, transfer\nfiles, use a secure and transparent tunnel for your remote programs. With its\nSecure FTP implementation, you can play with remote files easily, without\nthird-party programs others than libcrypto (from openssl).\r\n\r\nSecurity Fix(es):\n\nA flaw was found in libssh when using the ChaCha20 cipher with the OpenSSL library. If an attacker manages to exhaust the heap space, this error is not detected and may lead to libssh using a partially initialized cipher context. This occurs because the OpenSSL error code returned aliases with the SSH_OK code, resulting in libssh not properly detecting the error returned by the OpenSSL library. This issue can lead to undefined behavior, including compromised data confidentiality and integrity or crashes.(CVE-2025-5987)",
"id": "OESA-2025-2131",
"modified": "2026-08-06T11:09:13Z",
"published": "2025-09-05T11:09:13Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2131"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-5987"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "libssh security update",
"upstream": [
"CVE-2025-5987"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.