CVE-2013-10065

Sysax Multi Server vulnerability

7.5 HIGHPublic exploitEPSS 1.70%

Published5 Aug 2025

Description

A denial-of-service vulnerability exists in Sysax Multi-Server version 6.10 via its SSH daemon. A specially crafted SSH key exchange packet can trigger a crash in the service, resulting in loss of availability. The flaw is triggered during the handling of malformed key exchange data, including a non-standard byte (\x28) in place of the expected SSH protocol delimiter.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityNone

IntegrityNone

AvailabilityHigh

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

Affected products

Sysax Multi Server6.10

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/auxiliary/dos/windows/ssh/sysax_sshd_kexchange.rbExploit
https://www.mattandreko.com/2013/04/08/sysax-multi-server-6.10-ssh-dos/ExploitThird Party Advisory
https://www.sysax.com/Product
https://www.vulncheck.com/advisories/sysax-multi-server-sshd-key-exchange-dosThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2013-10065 being actively exploited?

CVE-2013-10065 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.70%.

How severe is CVE-2013-10065?

CVE-2013-10065 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 1.70% probability of exploitation.

Which products are affected by CVE-2013-10065?

Affected products include Sysax Multi Server.

How do I fix CVE-2013-10065?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2013-10065 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.