A buffer overflow vulnerability exists in the c1sizer ActiveX control (C1sizer.ocx) in IBM SPSS SamplePower 3.0 prior to FP1. The flaw is due to improper buffer size checking in the TabCaption property, specifically when handling strings with lstrcatA, allowing remote attackers to execute arbitrary code if a user visits a malicious website using Internet Explorer with the vulnerable control installed.
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 (ibm_spss_c1sizer.rb) that exploits a heap-based buffer overflow in the C1Tab ActiveX control (c1sizer.ocx) as distributed with IBM SPSS SamplePower 3.0. The exploit targets users running Internet Explorer 6, 7, or 8 on Windows XP SP3 or Windows 7. The module sets up a malicious HTTP server that serves a crafted HTML/JavaScript page, which performs a heap spray and triggers the overflow via the TabCaption property of the ActiveX control. Successful exploitation results in arbitrary code execution in the context of the browser. The module allows for customizable payloads and includes targeting logic for different IE/Windows versions. The only fingerprintable endpoints are the vulnerable OCX file and a reference to the IBM advisory. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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.