Loading vulnerability…
A vulnerability in the lpd daemon (in.lpd) in Solaris 8 and earlier allows remote attackers to execute arbitrary commands. The issue arises when a job request with a specially crafted control file is submitted, which is not properly sanitized before being passed to a mail program invoked by lpd. This improper handling enables command injection via the control file.
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 (3 hidden).
This repository contains a single Metasploit module: 'modules/exploits/solaris/lpd/sendmail_exec.rb'. The module exploits an arbitrary command execution vulnerability (CVE-2001-1583) in the in.lpd service on Sun Solaris systems up to version 8.0. The exploit works by uploading specially crafted control and configuration files to the print spool directory ('/var/spool/print') via the LPD protocol (TCP port 515). These files are designed to trick the service into executing an attacker-supplied shell script using /bin/sh. The module allows the attacker to specify a custom command payload, which is then executed on the target system. The exploit is operational and provides remote command execution capabilities. The only network endpoint involved is the LPD service on TCP port 515. The repository is structured as a standard Metasploit exploit module, written in Ruby, and is intended for use within 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.