Loading vulnerability…
A stack-based buffer overflow exists in the Novell iPrint Client for Windows (version 5.52), specifically in the ienipp.ocx ActiveX control. The vulnerability is triggered by passing an overly long argument to the GetDriverSettings2 method, which can be reached via the GetDriverSettings method. This allows remote attackers to execute arbitrary code in the context of the user, typically via a malicious web page or file that instantiates the vulnerable ActiveX control.
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 targeting a stack buffer overflow vulnerability in the Novell iPrint Client 5.52 ActiveX control (ienipp.ocx), specifically in the GetDriverSettings() method. The exploit is delivered via a malicious HTML page served by the attacker's HTTP server. When a victim using Internet Explorer (6 or 7) on Windows XP or Vista visits the page, the exploit triggers the buffer overflow, allowing arbitrary code execution with the user's privileges. The module is operational and allows the attacker to specify a custom payload (e.g., reverse shell, meterpreter). The main attack vector is browser-based, exploiting a vulnerable ActiveX control via a crafted web page. The module references CVE-2010-4321 and is designed for use within the Metasploit framework. The only file present is the exploit module itself, written in Ruby.
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.
1 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.