Loading vulnerability…
A stack-based buffer overflow exists in the pcspref.dll component of pcsws.exe in IBM Personal Communications versions 5.9.x before 5.9.8 and 6.0.x before 6.0.4. The vulnerability is triggered when a user opens a specially crafted WorkStation (.ws) file containing an overly long profile string, leading to a buffer overflow condition. This flaw allows remote attackers to potentially execute arbitrary code in the context of the user running the application.
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_pcm_ws.rb) that exploits a stack-based buffer overflow vulnerability (CVE-2012-0201) in IBM Personal Communications I-Series Access WorkStation 5.9. The exploit targets the parsing of WorkStation profile files (.ws) by the pcsws.exe application, specifically in the pcspref.dll library. By crafting a malicious .ws file, the exploit achieves arbitrary code execution when the file is opened by a user on a vulnerable system. The module includes advanced techniques to bypass DEP and ASLR mitigations on Windows XP, Vista, and 7. The payload is customizable and delivered via the malicious file. The repository is structured as a standard Metasploit module, written in Ruby, and leverages the Metasploit framework's file format exploitation capabilities. No network endpoints are involved; exploitation is achieved via local file execution.
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.