In NSPR API versions 4.6.1 and 4.6.2, as used in Sun Solaris 10, the library trusts user-specified environment variables to determine log file locations, even when invoked from setuid programs. This allows a local attacker to specify arbitrary file paths for log output, leading to the creation or overwriting of files with the privileges of the setuid program.
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 (5 hidden).
This repository contains a single Metasploit module: 'Solaris libnspr NSPR_LOG_FILE Privilege Escalation'. The exploit targets a local privilege escalation vulnerability (CVE-2006-4842) in the Netscape Portable Runtime library (libnspr) on unpatched Solaris systems prior to Solaris 10u3 with libnspr versions before 4.6.3. The vulnerability allows an unprivileged user to write arbitrary files as root by abusing the NSPR_LOG_FILE environment variable in conjunction with a SUID binary linked to the vulnerable library. The module writes a malicious shared object to /usr/lib/secure, uploads and compiles a payload, and then executes the SUID binary with a manipulated LD_LIBRARY_PATH to load the malicious library, resulting in execution of the payload as root. The exploit is operational and provides root access if successful. The code is written in Ruby and is structured as a standard Metasploit local exploit module.
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.