Novell iPrint Client for Windows versions before 4.36 contain multiple stack-based buffer overflows in the ActiveX control implemented by ienipp.ocx. Supplying an overly long value to the operation, printer-url, or target-frame parameter can overflow a stack buffer and allow remote code execution.
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 exploit module targeting a stack buffer overflow vulnerability in the Novell iPrint Client ActiveX control (ienipp.ocx), specifically the GetDriverSettings() method. The exploit is delivered via a malicious HTML page served by the Metasploit framework's HTTP server. When a vulnerable client (Windows XP or Vista running Internet Explorer 6 or 7 with Novell iPrint Client 4.34 installed) visits the page, JavaScript code triggers the buffer overflow, allowing arbitrary code execution. The module supports customizable payloads as provided by Metasploit, and the attack vector is browser-based, requiring user interaction (visiting the attacker's page). The main fingerprintable endpoint is the ActiveX CLSID (36723F97-7AA0-11D4-8919-FF2D71D0D32C) and the vulnerable ienipp.ocx file. The repository is structured as a single Ruby file following Metasploit's exploit module conventions.
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.