Loading vulnerability…
GAMSoft TelSrv telnet server versions 1.5 and earlier contain a vulnerability where supplying an excessively long username during the authentication process can cause the server to crash, resulting in a denial of service. The vulnerability is likely due to improper bounds checking on the username input, leading to a buffer overflow or similar memory corruption issue.
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 exploit module targeting a stack buffer overflow vulnerability in the username handling of GAMSoft TelSrv 1.5 (CVE-2000-0665). The exploit works by sending an overly long username to the TelSrv service running on TCP port 23 (Telnet). The module supports multiple targets, primarily Windows 2000 Pro SP0/4 English, and allows for customizable payloads using the Metasploit framework. The exploit is operational: it provides code execution on the target, but the TelSrv service will crash after exploitation, allowing only a single attempt per service restart. The code is written in Ruby and follows standard Metasploit module structure, with clear separation of check and exploit routines. The only endpoints referenced are the default Telnet port (23) and a URL to the vulnerable software. The module is not a detection script and is not fake; it is a real exploit for a known vulnerability.
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.