Loading vulnerability…
A stack-based buffer overflow vulnerability exists in IcoFX 2.5.0.0 and earlier for Windows. The vulnerability is triggered when the application processes a specially crafted ICO file containing a long idCount value in the ICONDIR structure. This allows an attacker to overwrite the Exception Handler and execute arbitrary code if a user opens a malicious ICO file. The vulnerability is client-side and requires user interaction to exploit. The issue was discovered by Marcos Accossatto of Core Exploit Writers Team and published by Core Security Technologies. The vendor did not respond to disclosure attempts, and no official patch is available.
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 module (modules/exploits/windows/fileformat/icofx_bof.rb) that exploits a stack-based buffer overflow vulnerability (CVE-2013-4988) in IcoFX version 2.5 on Windows 7 SP1. The exploit works by generating a specially crafted .ico file (default name: msf.ico) with a malformed ICONDIR header and a large number of ICONDIRENTRY structures, which triggers a buffer overflow when parsed by the vulnerable application. The module allows the attacker to embed a Metasploit payload (up to 864 bytes) into the .ico file, enabling arbitrary code execution when the file is opened by a victim. The exploit is operational and leverages local attack vectors, as it requires user interaction to open the malicious file. 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.