A stack-based buffer overflow exists in Novell iPrint Client versions prior to 5.44. The vulnerability is triggered when a remote attacker sends a specially crafted op-client-interface-version action containing an excessively long call-back-url parameter, leading to a buffer overflow on the stack.
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 (2 hidden).
This repository contains a single Metasploit module (novelliprint_callbackurl.rb) that exploits a stack-based buffer overflow vulnerability (CVE-2010-1527) in the Novell iPrint Client ActiveX control (ienipp.ocx) versions 5.40 and 5.42. The exploit targets users running Internet Explorer 6 or 7 on Windows XP SP3 or Windows Vista SP2. The module sets up a malicious HTTP server that serves a crafted HTML page containing JavaScript and an <object> tag referencing the vulnerable ActiveX control. By supplying an overly long string to the 'call-back-url' parameter, the exploit triggers a buffer overflow, allowing arbitrary code execution (Metasploit payload) on the victim's machine. The exploit is fully weaponized, leveraging Metasploit's payload system for customizable post-exploitation actions. The main fingerprintable endpoints are the CLSID of the vulnerable control and the ienipp.ocx file. The repository is structured as a single Ruby file compatible with the Metasploit Framework.
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.