CVE-1999-0113 is an argument injection vulnerability in some implementations of rlogin. The flaw occurs when attacker-supplied input such as the "-froot" parameter is passed to another program without proper delimitation or neutralization of command-line arguments. In the vulnerable execution path, the "-f" option is interpreted by the downstream program as a request to execute as user root, resulting in unintended privileged execution. This is a canonical example of CWE-88, Improper Neutralization of Argument Delimiters in a Command.
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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Canonical argument injection example where a crafted argument changes execution context to root.
Canonical argument injection example where a crafted argument changes execution context to run as root.
Canonical argument-injection example where an attacker-supplied argument (e.g., -froot) is forwarded to another program and changes execution context/privileges (e.g., running as root).
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.