Loading vulnerability…
An off-by-one error exists in the channel code of OpenSSH versions 2.0 through 3.0.2. This vulnerability allows a local user or a remote malicious server to exploit the flaw, potentially leading to privilege escalation. The error occurs due to improper bounds checking in the handling of channel data structures.
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 (2 hidden).
This repository provides a proof-of-concept (PoC) pentest environment for CVE-2002-0083, an off-by-one vulnerability in Dropbear SSH's channel boundary checking. The main exploit script (cve_2002_0083_pentest.py) authenticates to a Dropbear SSH server, opens multiple channels, and sends a message to an invalid channel index to test for the vulnerability. The result is determined by whether the server crashes (vulnerable) or properly rejects the request (patched). The repository includes Dockerfile and shell scripts to build and run Dropbear in a controlled environment, as well as Python modules for orchestrating tests and managing the environment. The structure is modular, with clear separation between environment setup, server management, and vulnerability evaluation. The attack vector is network-based, targeting the SSH service on TCP port 2222. Several file and network endpoints are used for configuration, key management, and test execution. The repository is focused on detection and verification of the vulnerability, not on weaponization or post-exploitation.
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, 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.