A buffer overflow vulnerability exists in mIRC versions prior to 6.11, where the application fails to properly handle long irc:// URLs. This flaw allows remote attackers to trigger a buffer overflow condition by enticing a user to open a specially crafted irc:// URL, potentially leading to the execution of arbitrary code within the context of the user running mIRC.
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 (mirc_irc_url.rb) that exploits a stack buffer overflow vulnerability in mIRC version 6.1 (CVE-2003-1336). The exploit is delivered via a malicious web server that serves an HTML page containing an iframe with a specially crafted irc:// URL. When a victim with a vulnerable version of mIRC installed visits the page, the irc:// URL is processed, triggering the buffer overflow and allowing arbitrary code execution. The module supports custom Metasploit payloads (up to 400 bytes, with specific bad characters avoided) and targets Windows 2000 Pro (English) and Windows XP Pro SP0/SP1 (English). The main attack vector is browser-based social engineering, requiring the victim to visit the attacker's web page. The only fingerprintable endpoint is the crafted irc:// URL embedded in the HTML response.
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.