CVE-2008-4109 is a denial-of-service vulnerability in certain patched OpenSSH packages, notably Debian-derived builds before the listed fixed releases, caused by an incorrect fix for CVE-2006-5051. The affected patch causes the sshd login-timeout signal handler to invoke functions that are not async-signal-safe when handling authentication timeouts. A remote attacker can repeatedly trigger the timeout path through multiple login attempts, causing sshd to mishandle connection cleanup and exhaust available connection slots.
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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An older OpenSSH vulnerability/fix reference mentioned because it was an incorrect fix for CVE-2006-5051 and is relevant to determining exposure to CVE-2024-6387 in older versions.
Older OpenSSH vulnerability referenced only to define when very old OpenSSH versions remain affected by CVE-2024-6387 if prior fixes were not applied.
An older OpenSSH vulnerability mentioned in versioning and patch-status context for determining exposure of older OpenSSH releases.
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.