A vulnerability in OpenSSH 6.x and 7.x through 7.3 exists in the kex_input_kexinit function in kex.c, where remote attackers can cause excessive memory consumption by sending many duplicate KEXINIT requests. This can lead to a denial of service condition.
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 proof-of-concept exploit for CVE-2016-8858, targeting OpenSSH servers. The main code is in 'src/kexkill.c', a C program that connects to a specified SSH server and sends a stream of SSH KEXINIT packets. This triggers excessive memory usage on vulnerable OpenSSH versions, potentially leading to denial of service. The exploit is configurable for the number of concurrent connections and supports verbose output. The repository includes standard build files and a README describing the vulnerability and usage. No hardcoded IPs or domains are present; the target is specified at runtime. The exploit demonstrates the vulnerability but does not provide a weaponized or automated attack framework.
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 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.