Loading vulnerability…
CVE-2012-10057 is a stack-based buffer overflow in Lattice Semiconductor ispVM System v18.0.2 during parsing of .xcf project files. Specifically, when the application processes the version attribute of the ispXCF XML tag, it does not properly validate the input length before copying or handling the value, allowing a specially crafted .xcf file to overwrite stack memory. An attacker can exploit this by convincing a user to open a malicious project file, which may lead to arbitrary code execution in the security context of the user running ispVM System.
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 module targeting a buffer overflow vulnerability (CVE-2012-10057) in Lattice Semiconductor's ispVM System version 18.0.2 for Windows. The exploit works by generating a malicious .xcf file with an overly long 'version' attribute in the 'ispXCF' XML tag, which triggers a buffer overflow when opened by the vulnerable application. The module allows the attacker to specify a payload, which is encoded and inserted into the crafted file. When a victim opens the file, arbitrary code is executed with the privileges of the user. The exploit is operational and leverages a hardcoded return address from MSVCP60.dll. The repository is structured as a single Ruby file compatible with the Metasploit framework, and does not contain any network-based attack vectors; exploitation is achieved via local file execution. Notable fingerprintable endpoints include the generated malicious file ('msf.xcf') and the use of a specific DLL for the return address.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.