Client or server crash via cipher cleanup
Published Apr 13, 2020 · Updated Aug 4, 2024
NULL pointer dereference in libssh 0.8.0 through 0.8.8 and 0.9.0 through 0.9.3 allows remote attackers to crash clients or servers. The OpenSSL cipher cleanup path dereferences an uninitialized AES-CTR context when an incomplete connection closes. A malicious SSH peer can trigger the fault without authentication; a prefork server confines the crash to one session process.
Summary
What happened
NULL pointer dereference in libssh 0.8.0 through 0.8.8 and 0.9.0 through 0.9.3 allows remote attackers to crash clients or servers. The OpenSSL cipher cleanup path dereferences an uninitialized AES-CTR context when an incomplete connection closes. A malicious SSH peer can trigger the fault without authentication; a prefork server confines the crash to one session process.
The record
- CVE
- CVE-2020-1730
- Published
- Apr 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- libssh
- Product
- libssh
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 13, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=libssh versions before 0.8.9
- Affected versionversion=libssh versions before 0.9.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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