CVE-2012-10060
Sysax Multi Server remote code execution
- Published13 Aug 2025
Description
Sysax Multi Server versions prior to 5.55 contain a stack-based buffer overflow in its SSH service. When a remote attacker supplies an overly long username during authentication, the server copies the input to a fixed-size stack buffer without proper bounds checking. This allows remote code execution under the context of the service.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://advisories.checkpoint.com/defense/advisories/public/2012/cpai-23-sepc.html
- https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/windows/ssh/sysax_ssh_username.rb
- https://web.archive.org/web/20120302203344/http://www.pwnag3.com/2012/02/sysax-multi-server-ssh-username-exploit.html
- https://www.exploit-db.com/exploits/18535
- https://www.exploit-db.com/exploits/18557
- https://www.sysax.com/
- https://www.vulncheck.com/advisories/sysax-multi-server-ssh-username-buffer-overflow
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2012-10060 being actively exploited?
CVE-2012-10060 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 4.31%.
How severe is CVE-2012-10060?
CVE-2012-10060 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 4.31% probability of exploitation.
Which products are affected by CVE-2012-10060?
Affected products include Sysax Multi Server.
How do I fix CVE-2012-10060?
Upgrade affected software to a fixed version, for example Sysax Multi Server 5.55 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2012-10060 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.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.