A buffer overflow vulnerability exists in ShixxNote 6.net build 117 due to improper handling of input in the font field. Remote attackers can exploit this flaw by sending a specially crafted request with an overly long font field, leading to a buffer overflow condition.
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 (modules/exploits/windows/misc/shixxnote_font.rb) that exploits a buffer overflow vulnerability (CVE-2004-1595) in ShixxNOTE 6.net. The exploit targets the application's handling of font fields, allowing an attacker to send a specially crafted payload over TCP port 2000 to trigger a Structured Exception Handler (SEH) overwrite and execute arbitrary code. The module is fully integrated with Metasploit, supporting customizable payloads and automated exploitation. The only fingerprintable endpoint is the default TCP port 2000 used by the vulnerable service. The exploit is weaponized, allowing for reliable remote code execution on affected Windows systems running ShixxNOTE 6.net.
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.