Loading vulnerability…
OpenSSH sshd before version 7.4 contains a flaw that allows a remote attacker to crash the daemon by sending a specially crafted out-of-sequence NEWKEYS message during the SSH protocol exchange. The issue is related to handling in kex.c and packet.c and results in a NULL pointer dereference in sshd. Successful exploitation terminates the daemon handling the connection, causing a denial of service.
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.
This repository contains a Python proof-of-concept exploit for CVE-2016-10708, a denial-of-service vulnerability in OpenSSH versions prior to 7.4. The main file, 'poc.py', is a standalone script that can operate in two modes: 'scan' and 'attack'. In scan mode, it connects to one or more SSH servers, retrieves their banners, and determines if they are running a vulnerable version of OpenSSH. In attack mode, it opens multiple simultaneous TCP connections to the target(s) and floods them with specially crafted SSH_MSG_NEWKEYS packets, exploiting the vulnerability to potentially crash or destabilize the SSH daemon. The script is multi-threaded, configurable via command-line arguments, and does not require any third-party dependencies. The only code file is 'poc.py'; the other files are a README and a license. The exploit targets network-accessible SSH services, defaulting to port 22 but allowing customization. No hardcoded IPs or domains are present; targets are supplied by the user at runtime.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.