Data compromise or crash via status-code collision
Published Jul 7, 2025 · Updated Aug 31, 2026
Improper error handling in libssh 0.10.0 through 0.11.1 allows remote attackers to compromise SSH data or crash applications. In chacha20_poly1305_set_key(), an OpenSSL initialization failure returns 0, which aliases SSH_OK, so libssh continues with a partially initialized cipher context. Exploitation requires an OpenSSL build, ChaCha20-Poly1305 use, and attacker-driven heap exhaustion; consequences include loss of data confidentiality or integrity and an application crash.
Summary
What happened
Improper error handling in libssh 0.10.0 through 0.11.1 allows remote attackers to compromise SSH data or crash applications. In chacha20_poly1305_set_key(), an OpenSSL initialization failure returns 0, which aliases SSH_OK, so libssh continues with a partially initialized cipher context. Exploitation requires an OpenSSL build, ChaCha20-Poly1305 use, and attacker-driven heap exhaustion; consequences include loss of data confidentiality or integrity and an application crash.
The record
- CVE
- CVE-2025-5987
- Published
- Jul 7, 2025
- Updated
- Aug 31, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat OpenShift Container Platform 4.16
- Classifications
- CWE-393, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 7, 2025CVE publishedPublication date reported by the CVE source.
- Aug 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo