Loading vulnerability…
A buffer overflow vulnerability exists in Van Dyke SecureCRT SSH client versions prior to 3.4.6 and 4.x prior to 4.0 beta 3. The vulnerability is triggered when the client receives an excessively long SSH1 protocol version string from a malicious SSH server, leading to a buffer overflow condition. This can allow the attacker to execute arbitrary code on the client system.
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 exploit module targeting a buffer overflow vulnerability in SecureCRT (<= 4.0 Beta 2, tested on 3.4.4) for Windows. The exploit works by acting as a malicious SSH1 server: when a vulnerable SecureCRT client connects, the server sends an overly long SSH1 protocol identifier string, triggering a buffer overflow and allowing arbitrary code execution on the client. The module is written in Ruby and leverages Metasploit's payload system, allowing for customizable payloads (such as reverse shells). The only network endpoint is the TCP port (default 22) on which the fake SSH server listens. The exploit is operational and requires the victim to initiate a connection to the attacker's 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.
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.