The default installation of sadmind on Solaris employs weak authentication using AUTH_SYS, which can be easily spoofed. This allows both local and remote attackers to impersonate legitimate Solstice AdminSuite clients by crafting a specific sequence of RPC packets, ultimately enabling them to gain root privileges on the target system.
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/solaris/sunrpc/sadmind_exec.rb) that exploits a remote command execution vulnerability in the Sun Solstice AdminSuite sadmind RPC service (CVE-2003-0722) on Solaris 2.7, 8, and 9. The exploit works by sending a specially crafted SunRPC request to the sadmind service (program number 100232, version 10) over UDP, leveraging weak default security settings to execute arbitrary shell commands as root. The module is fully integrated into the Metasploit framework, allowing for customizable payloads (typically command shells or reverse shells) and supporting various command encoders. The main attack vector is network-based, targeting the sadmind RPC service. Notable endpoints include the sadmind RPC program/version, the use of /bin/sh for command execution, and the loopback IP address in the RPC header. The code is mature and weaponized, providing reliable exploitation capabilities for penetration testers and red teamers.
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.