CVE-1999-0502 describes a Unix account configured with a default, null, blank, or missing password. Such configurations can allow unauthorized authentication using known default credentials or without supplying a password, depending on the authentication mechanism. A related demonstration obtained root access to a retail digital video recorder using default credentials less than five minutes after powering it on.
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 (24 hidden).
This repository contains a single Metasploit module: 'modules/exploits/multi/ssh/sshexec.rb'. The module is designed to exploit systems accessible via SSH by leveraging weak or known credentials (CVE-1999-0502). It supports a wide range of platforms, including Linux, OSX, BSD, Unix, and Python-enabled systems. The exploit works by authenticating to the target SSH server using provided credentials and then executing arbitrary commands or payloads, which can include reverse shells, command stagers, or interactive SSH sessions. The module is highly weaponized, allowing for flexible payload delivery and session management. The only fingerprintable endpoint is the SSH service, typically on TCP port 22, but the port is configurable. The code is structured as a standard Metasploit exploit module, with options for username, password, target host, and port, and includes advanced options for SSH debugging. The exploit is not a detection script or a fake; it is a fully operational code execution module for post-authentication SSH access.
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.
3 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.