CatalogregreSSHion
regreSSHion (CVE-2024-6387)
Shared component regresshion
Signal-handler race condition in OpenSSH server (sshd) on glibc-based Linux that can yield unauthenticated remote code execution as root. CVSS 8.1. Qualys demonstrated exploitability in the lab. Broad downstream blast radius across distros and appliances. Not in CISA KEV as of 23 Oct 2026.
- Aliases
- Published
- Updated
What the bug is
regreSSHion is Qualys's name for CVE-2024-6387, a signal-handler race condition in OpenSSH's server (sshd). If a client does not authenticate within LoginGraceTime (120 seconds by default), sshd's SIGALRM handler runs asynchronously and calls functions that are not async-signal-safe, such as syslog(), on glibc-based Linux. An unauthenticated remote attacker may obtain code execution as root.
OpenSSH 9.8 (released 1 Jul 2024) fixes the issue. Portable OpenSSH versions 8.5p1 through 9.7p1 (inclusive) are vulnerable. Versions from 4.4p1 up to but not including 8.5p1 are not vulnerable to this regression. OpenBSD is not vulnerable. Qualys demonstrated successful exploitation on 32-bit Linux/glibc with ASLR under lab conditions (about 6-8 hours of continuous connections). Exploitation on 64-bit systems was believed possible but not demonstrated at disclosure.
Qualys identified over 14 million potentially vulnerable OpenSSH server instances exposed to the internet via Censys and Shodan searches. The bug is a regression of CVE-2006-5051.
Attack path
- Many connectionsAttacker opens many unauthenticated SSH connections that sit until LoginGraceTime.
- SIGALRM raceThe SIGALRM handler runs and calls async-signal-unsafe functions in a racy way.
- Memory corruptionThe race can corrupt memory in sshd. ASLR and timing make reliable exploitation hard.
- Root code execSuccessful exploitation yields code execution as root. Conceptual impact class only.
High-level only. Not a reproduction guide.
Exploitation status
CISA KEV
Not in CISA KEV as of .
Last verified 23 Oct 2026 against CISA KEV catalog 2026.10.21. CVE-2024-6387 is not listed.
First seen
No first-seen source recorded.
No authoritative source in the pack confirms in-the-wild compromise. Qualys demonstrated a working exploit privately to the OpenSSH team and did not release it.
What defenders should do today
Do today
- 1
Upgrade OpenSSH / apply vendor packages
Move to OpenSSH 9.8p1 or later, or install your distribution or vendor patch (for example Ubuntu 1:9.6p1-3ubuntu13.3 on 24.04, RHEL 9 RHSA-2024:4312, Amazon Linux 2023 ALAS2023-2024-649).
This week
- 1
Interim LoginGraceTime workaround if you cannot patch
Ubuntu documents setting LoginGraceTime 0 in sshd_config. That avoids the race but makes sshd vulnerable to MaxStartups exhaustion DoS. Prefer patching.
- 2
Restrict SSH exposure
Limit sshd to trusted networks or require a bastion/VPN. Qualys reported multi-million-scale internet exposure of potentially vulnerable instances.
- 3
Patch appliances that ship OpenSSH
Cisco, Fortinet, and others published product advisories. Appliance OpenSSH is not covered by the host OS package alone.
Detection rules
Sigma
OpenSSH Timeout Before Authentication
title: OpenSSH Timeout Before Authentication id: 02a549cd-caf6-5a1e-bb3d-3652385d99ec status: experimental description: Matches sshd "Timeout before authentication" messages. Exploiting CVE-2024-6387 (regreSSHion) needs thousands of connections held until LoginGraceTime, so a sharp rise in these messages on an unpatched host is the signal. Alert on volume per host or source, not single events. references: - https://www.splunk.com/en_us/blog/security/cve-2024-6387-regresshion-vulnerability.html - https://www.qualys.com/2024/07/01/cve-2024-6387/regresshion.txt author: vuln2shell date: 2026-10-23 tags: - attack.initial-access - attack.t1190 - cve.2024-6387 logsource: product: linux service: sshd detection: keywords: - 'Timeout before authentication' condition: keywords falsepositives: - Internet scanners and brute-force noise also produce this message level: lowBy vuln2shell, . Source. License: CC0 1.0
Written by vuln2shell. Untested, tune before use.
Sigma form of the Splunk blog search. Pair it with a count threshold in your SIEM.
SPL (Splunk)
Timeout before authentication by host
sourcetype=journald OR sourcetype=linux:auth OR TERM(sshd) OR TERM(ssh) TERM(Timeout) TERM(authentication) "Timeout before authentication" | timechart count by hostBy Splunk Threat Research Team, . Source. License: Posted publicly; see source
Look for spikes on hosts still on OpenSSH 8.5p1 to 9.7p1.
KQL (Microsoft Sentinel / Defender)
KQL for detecting potential RegreSSHion abuse
// KQL for detecting potential hashtag#RegreSSHion abuse // https://www.linkedin.com/posts/activity-7214588446722465792-FwFr/ // ** Assumption ** // Firewall logs stream to CommonSecurityLog // 6 OpenSSH connections per min for minimum 6 hours // 6x60x6 = 2160 connections for past 6 hours // Attack source is non-distributed, triangulate by country level // Feel free to adjust the assumption parameters to your environment needs CommonSecurityLog | where TimeGenerated >= ago (6h) | where DestinationPort == "22" | extend ip_location=geo_info_from_ip_address(SourceIP) | extend Country=tostring(ip_location.country) | where Country != "" | summarize SSH_Connection=count() by Country | sort by SSH_Connection desc | where SSH_Connection > 2160 // If analytics rule get triggered, this probably warrant a deeper investigationBy Steven Lim (@0x534c), . Source. License: BSD-3-Clause (repo LICENSE)
Excerpt; the file's MITRE mapping comments are omitted. Author asks for credit to Steven Lim / @SlimKQL when reused.
DefenderXDR Exposure Management for RegreSSHion
Exposure check// DefenderXDR Exposure Management for hashtag#RegreSSHion // https://www.linkedin.com/posts/activity-7214788756237639680-rGkW/ //Use below KQL to determine your internet facing VM with OpenSSH and prioritize the following: // - Access Control // - Host-based Intrusion Prevention (E.g fail2ban) // - SSH Configuration Hardening // (E.g LoginGraceTime/MaxStartups/PerSourceMaxStartups) // Refer to Splunk Mitigation Strategies for CVE-2024-6387 // Link: https://lnkd.in/gFPsbcaW let InternetFacingVM= ExposureGraphNodes | where NodeLabel == 'device' or (Categories has 'virtual_machine' and set_has_element(Categories, 'virtual_machine')) | where NodeProperties.rawData.isInternetFacing == true | extend InternetFacingDeviceName=tostring(NodeProperties.rawData.deviceName) | project InternetFacingDeviceName; DeviceTvmSoftwareInventory | where SoftwareName contains "openssh" | where DeviceName has_any(InternetFacingVM)By Steven Lim (@0x534c), . Source. License: BSD-3-Clause (repo LICENSE)
Excerpt; MITRE comments omitted. Lists internet-facing devices with OpenSSH installed, for prioritising.
LogScale (CrowdStrike)
OpenSSH Timeout before authentication by source (LogScale)
"Timeout before authentication" | regex("for (?<src_ip>\S+) port") | groupBy([src_ip], function=count(as=timeouts)) | sort(timeouts, order=desc)By vuln2shell, . Source. License: CC0 1.0
Written by vuln2shell. Untested, tune before use.
Free-text search, so it works with any Linux auth parser.
Suricata / Snort
ET INFO Server Responded with Vulnerable OpenSSH Version (CVE-2024-6387)
#alert ssh any any -> [$HOME_NET,$HTTP_SERVERS] any (msg:"ET INFO Server Responded with Vulnerable OpenSSH Version (CVE-2024-6387)"; flow:established,to_client; content:"SSH-"; startswith; content:"-OpenSSH_"; fast_pattern; pcre:"/^(?:[123]|4\.(?:[0123](?:p\d)?|4[^p])|8\.(?:[6789](?:p\d)?|5(?:p[^1])?)|9\.(?:[01234567](?:p\d)?|8[^p]))(?:\.\d)*(?:\d|p\d)*/R"; reference:cve,2024-6387; reference:url,blog.qualys.com/vulnerabilities-threat-research/2024/07/01/regresshion-remote-unauthenticated-code-execution-vulnerability-in-openssh-server; classtype:successful-recon-largescale; sid:2054218; rev:2; metadata:attack_target Client_and_Server, created_at 2024_07_01, cve CVE_2024_6387, deployment Perimeter, deployment Internal, former_category EXPLOIT, performance_impact Significant, confidence High, signature_severity Informational, tag Description_Generated_By_Proofpoint_Nexus, updated_at 2024_07_02, former_sid 2857461, mitre_tactic_id TA0001, mitre_tactic_name Initial_Access, mitre_technique_id T1190, mitre_technique_name Exploit_Public_Facing_Application; target:dest_ip;)By Emerging Threats (Proofpoint), . Source. License: BSD-3-Clause (ET Open, sids 2000000-2799999)
Flags servers whose banner shows a vulnerable OpenSSH version. Distro backports can make patched builds match. Ships commented out (disabled) in ET Open; enable it to use it.
More detection content
- Qualys: regreSSHion technical advisory
By Qualys Threat Research Unit,
- Splunk: regreSSHion detection and mitigation
By Splunk Threat Research Team, . Also has an OpenSSH package inventory search.
- Steven Lim: Leveraging Sentinel UEBA to safeguard against OpenSSH exploits
By Steven Lim (@0x534c),
- Steven Lim: Azure Resource Graph check for Linux VMs running OpenSSH
By Steven Lim (@0x534c)
Affected products
Products that share
OpenBSD is not vulnerable. Many enterprise Linux releases before OpenSSH 8.5p1 are outside the regression window and vendors state not affected.
| Product | Status | Fixed version / ETA | Advisory | Notes |
|---|---|---|---|---|
| Linux distributions9 | ||||
| Amazon Linux 1 / 2Amazon | Vendor stated not affected | Not stated | Amazon Linux 1 and Amazon Linux 2 openssh Not Affected. AL1 and AL2 comes with OpenSSH version 7.4p1. | |
| Amazon Linux 2023Amazon | Affected | ALAS2023-2024-649 | Amazon Linux 2023 openssh Fixed, advisory ALAS2023-2024-649, release date 2024-07-01. | |
| Ubuntu 20.04 LTS (focal)Canonical | Vendor stated not affected | Not stated | openssh 20.04 LTS focal Not affected. | |
| Ubuntu 22.04 LTS (jammy)Canonical | Affected | 1:8.9p1-3ubuntu0.10 | openssh 22.04 LTS jammy Fixed in 1:8.9p1-3ubuntu0.10. | |
| Ubuntu 24.04 LTS (noble)Canonical | Affected | 1:9.6p1-3ubuntu13.3 | openssh 24.04 LTS noble Fixed in 1:9.6p1-3ubuntu13.3. | |
| OpenSSH PortableOpenSSH Project | Affected | 9.8 / 9.8p1 | A critical vulnerability in sshd(8) was present in Portable OpenSSH versions between 8.5p1 and 9.7p1 (inclusive). OpenBSD is not vulnerable. | |
| Red Hat Enterprise Linux 8 / 7 / 6Red Hat | Vendor stated not affected | Not stated | Red Hat Enterprise Linux 8, 7, and 6 package_state Not affected for openssh. | |
| Red Hat Enterprise Linux 9Red Hat | Affected | RHSA-2024:4312 (openssh-0:8.7p1-38.el9_4.1) | Red Hat Enterprise Linux 9 fixed via RHSA-2024:4312 on 2024-07-03. | |
| SUSE Linux Enterprise Server 15 SP6SUSE | Affected | openssh >= 9.6p1-150600.6.3.1 | SUSE Linux Enterprise Server 15 SP6 lists openssh >= 9.6p1-150600.6.3.1. SUSE states SLES 11 up to 15 SP5 are not affected. | |
| Network & security appliances2 | ||||
| Cisco ASA SoftwareCisco | Affected | 9.18.4.34 / 9.20.3 | Adaptive Security Appliance (ASA) Software CSCwk62296 fixed releases 9.18.4.34 and 9.20.3. | |
| FortiOSFortinet | Vendor stated not affected | Not stated | Products NOT Impacted: FortiOS, FortiProxy, FortiSASE, FortiClient EMS. | |
Timeline6
Key events
Newest first.
Fortinet publishes FG-IR-24-258 with product-specific fixed releases; FortiOS stated not impacted.
SourceRed Hat ships RHSA-2024:4312 for RHEL 9. RHEL 6/7/8 stated not affected.
SourceCisco publishes a multi-product regreSSHion advisory.
SourceOpenSSH 9.8 is released with the sshd race-condition fix. Qualys publishes regreSSHion.
SourceUbuntu publishes fixed openssh packages for noble, mantic, and jammy.
SourceAmazon Linux 2023 ships ALAS2023-2024-649. AL1/AL2 stated not affected (OpenSSH 7.4p1).
Source
Full timeline (6)
News & write-ups
PoC index (for defenders)
Public proof-of-concept links for defensive validation, with a source and a validation status.