Unauthenticated SSH service crash via malformed key exchange
Published Aug 5, 2025 · Updated Nov 21, 2025
Denial of service in the SSH daemon of Sysax Multi Server 6.10 allows remote attackers to crash the service with a crafted key exchange. Its key-exchange parser processes 0x28 in a field that expects 0x1a, causing an uncaught exception instead of rejecting the malformed packet. No authentication or user interaction is required, and the consequence is limited to interruption of the SSH service.
Summary
What happened
Denial of service in the SSH daemon of Sysax Multi Server 6.10 allows remote attackers to crash the service with a crafted key exchange. Its key-exchange parser processes 0x28 in a field that expects 0x1a, causing an uncaught exception instead of rejecting the malformed packet. No authentication or user interaction is required, and the consequence is limited to interruption of the SSH service.
The record
- CVE
- CVE-2013-10065
- Published
- Aug 5, 2025
- Updated
- Nov 21, 2025
- Vendor
- Codeorigin, LLC
- Product
- Sysax Multi Server
- Classifications
- CWE-248, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 5, 2025CVE publishedPublication date reported by the CVE source.
- Nov 21, 2025Record 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=6.10
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.
Public exploit references
- Sysax Multi-Server 6.10 SSHD Key Exchange Denial of Servicefunctional · demonstrated
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