CVE-2002-1359 affects multiple SSH2 server and client implementations that improperly handle oversized SSH packets or fields. Malformed packets supplied during SSH transport-layer key exchange or initialization can trigger buffer-overflow conditions. Affected implementations may crash, causing denial of service, or may permit execution of attacker-controlled code.
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 (1 hidden).
This repository contains a single Metasploit module exploit file: modules/exploits/windows/ssh/putty_msg_debug.rb. The module targets a buffer overflow vulnerability in the PuTTY SSH client (CVE-2002-1359), specifically affecting versions 0.53 and earlier on Windows platforms (Windows 2000 SP4, Windows XP SP2, Windows 2003 SP1). The exploit works by running a malicious SSH server (default port 22) that sends a specially crafted buffer to the connecting PuTTY client, triggering the overflow and executing arbitrary code (Metasploit payload) on the victim's machine. The exploit is operational and allows for customizable payloads, but requires the victim to initiate an SSH connection to the attacker's server. The code is written in Ruby and is designed to be used within the Metasploit framework.
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.