CVE-2013-3956 is a local privilege escalation vulnerability in the NICM.SYS kernel driver (version 3.1.11.0) used by Novell Client 4.91 SP5 (Windows XP/2003), Novell Client 2 SP2 (Windows Vista/Server 2008), and Novell Client 2 SP3 (Windows 7/8/Server 2008 R2/2012). The vulnerability is triggered by a crafted IOCTL 0x143B6B call, which allows a local attacker to execute arbitrary code in kernel mode, effectively hijacking execution flow within the driver.
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 (modules/exploits/windows/local/novell_client_nicm.rb) that exploits a local privilege escalation vulnerability (CVE-2013-3956) in the Novell Client 2 SP3 nicm.sys driver on Windows 7 SP1 (32-bit). The exploit abuses a vulnerable IOCTL handler (0x143B6B) in the driver, which allows a user-supplied pointer to be used as a function pointer in kernel space. The module allocates memory, writes a custom ring0 shellcode to steal the SYSTEM token, and triggers the vulnerability via DeviceIoControl on the \\.\nicm device. Upon successful exploitation, the attacker's privileges are elevated to SYSTEM, and a user-supplied Meterpreter payload is executed. The module is operational and requires a Meterpreter session on a compatible target. The only fingerprintable endpoint is the device path \\.\nicm, which identifies the presence of the vulnerable driver.
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, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.