Vulnerability in the Solaris component (Kernel) of Oracle Sun Systems Products Suite affecting Oracle Solaris 10 and 11. The issue is locally exploitable by a low-privileged authenticated user with logon access to the Solaris infrastructure, and can lead to compromise of Solaris. Reported outcomes include unauthorized update/insert/delete of some accessible data, unauthorized read access to a subset of accessible data, and the ability to cause a partial denial of service. CVSS v3.0: 5.3 (AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L).
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: 'Solaris RSH Stack Clash Privilege Escalation'. The module exploits a stack clash vulnerability in the setuid /usr/bin/rsh binary on unpatched Solaris 11.1 and 11.3 (x86) systems. The exploit works by uploading and compiling a C exploit (solaris_rsh.c by Qualys) on the target, which manipulates memory to create a SUID root shell. The module then uploads a Metasploit payload (default: cmd/unix/bind_netcat), marks it executable, and runs it as root via the newly created SUID shell. The exploit requires a local session on the target, a writable directory (default: /tmp), and gcc to be present. The module is weaponized, allowing for customizable payloads and automated cleanup. The only fingerprintable endpoints are the /usr/bin/rsh binary and the /tmp directory used for file operations. The code is structured as a standard Metasploit local exploit module, with options for target version, rsh path, and writable directory.
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.