Loading vulnerability…
CVE-2012-10060 affects Sysax Multi Server versions prior to 5.55. The vulnerability is a stack-based buffer overflow in the product's SSH service during authentication. A remote attacker can supply an overly long username, which is copied into a fixed-size stack buffer without proper bounds checking. This memory corruption condition can be leveraged to achieve remote code execution in the context of the affected service.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/windows/ssh/sysax_ssh_username.rb) that exploits a buffer overflow vulnerability in the Sysax Multi Server SSH service (CVE-2012-10060). The exploit targets Windows systems running Sysax SSH version 5.53 or earlier. By sending an overly long username during the SSH authentication process, the attacker can overflow a stack buffer and execute arbitrary code. The module supports both DEP and non-DEP targets, using either a regular stack-based exploit or a ROP chain as appropriate. The payload is customizable and encoded, with a maximum size of 1024 bytes, and is delivered as part of the SSH username field. The exploit is operational and provides remote code execution as the SSH service user. The only network endpoint required is the SSH service port (default 22), which can be configured. The module includes a check method to fingerprint the target by reading the SSH banner and confirming it is a vulnerable Sysax SSH server.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.