Loading vulnerability…
A vulnerability in OpenSSH versions 4.4 through before 4.9 allows remote authenticated users to bypass the ForceCommand directive specified in sshd_config by modifying their personal .ssh/rc session file. The ForceCommand directive is intended to restrict users to a specific command upon login, but this can be circumvented if the user is able to alter the .ssh/rc file, which is executed before the forced 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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
Small single-script Python repository centered on ssh-exploit.py, with supporting README, requirements, license, and .gitignore. The script uses Paramiko to connect to a user-supplied SSH target with hardcoded credentials 'msfadmin'/'msfadmin', then opens an interactive shell using invoke_shell(). It supports repeated command execution, captures returned output, and records simple proof-of-exploitation markers based on operator commands such as whoami, id, ls, cd, or access to /etc/passwd. After the session ends, it generates sequentially named DOCX and PDF reports in ./output using python-docx and reportlab. Although the README claims CVE-2008-0166 and CVE-2008-1657 exploitation against vulnerable OpenSSH services, the code does not contain CVE-specific exploit primitives, key generation attacks, brute force logic, or protocol manipulation; it is effectively an SSH post-authentication shell/reporting tool that depends on valid hardcoded credentials rather than directly exploiting the named vulnerabilities.
Small Python repository centered on a single script, ssh-exploit.py, with dependencies in requirements.txt and basic documentation in README.md. The script is presented as an SSH exploit for CVE-2008-0166 and CVE-2008-1657, but the actual implementation does not contain vulnerability-specific exploitation logic, key generation attacks, brute force, or protocol abuse. Instead, it uses Paramiko to connect to a user-supplied SSH target over port 22 with hardcoded credentials 'msfadmin'/'msfadmin'. If login succeeds, it launches an interactive shell via invoke_shell(), relays operator-entered commands, captures returned output, and tracks simple proof points based on commands like whoami, id, cd, ls, or references to passwd. After the session ends, it generates local DOCX and PDF reports in ./output summarizing the target, time, proof points, and command transcript. Repository structure is minimal: README.md describes intended use and output, requirements.txt lists paramiko, python-docx, and reportlab, and ssh-exploit.py contains all operational logic including argument parsing, SSH connection handling, shell interaction, logging, and report generation. Overall, this is an operational post-authentication remote shell wrapper and reporting utility rather than a true exploit for the claimed CVEs.
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.