freeSSHd.exe in freeSSHd through version 1.2.6 contains an authentication bypass vulnerability. Remote attackers can bypass SSH authentication by crafting a session, as demonstrated by using an OpenSSH client with modified ssh.c and sshconnect2.c files. The vulnerability is due to improper authentication checks in the SSH session handling code of freeSSHd.
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 (2 hidden).
This repository contains a single Metasploit module (freesshd_authbypass.rb) that exploits an authentication bypass vulnerability in FreeSSHd for Windows (versions <= 1.2.6, CVE-2012-6066). The exploit targets the SSH service (default port 22) and allows an attacker to bypass authentication using only a valid username (which can be supplied or brute-forced from a wordlist). Upon successful authentication bypass, the module can execute arbitrary payloads on the target, including PowerShell commands or staged command execution via VBS or CMD. The module is highly weaponized, leveraging Metasploit's payload and session management capabilities. The code is written in Ruby and is structured as a standard Metasploit exploit module, with options for specifying the target port, username, and user file. The main attack vector is network-based, targeting the SSH service. The only fingerprintable endpoints are the SSH port (22) and the optional username wordlist file.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.