Zum Hauptinhalt springen
LIVE Intel Feed
criticalCVSS 8.1/10·Published: 2024-07-01·OpenSSH

How to fix CVE-2024-6387 – Step-by-Step Guide

CVE-2024-6387, dubbed "OpenSSH regreSSHion," is a critical vulnerability affecting OpenSSH servers. This flaw allows unauthenticated remote code execution (RCE) as root. It poses a severe risk to systems running vulnerable OpenSSH versions.

CVE ID
CVE-2024-6387
Severity
CRITICAL
CVSS Score
8.1/10
Affected
OpenSSH

What is OpenSSH regreSSHion – Unauthenticated RCE?

This vulnerability stems from a signal handler race condition within the OpenSSH server (sshd) process. On glibc-based Linux systems, an attacker can exploit this race condition to achieve unauthenticated remote code execution. It specifically impacts OpenSSH versions 8.5p1 through 9.7p1.

Affected Versions
OpenSSH 8.5p1 – 9.7p1 (glibc Linux)
Fixed In
OpenSSH 9.8p1+

Impact and Risks for your Infrastructure

The primary impact is a full root compromise of the affected SSH server. Attackers can execute arbitrary code with root privileges without any prior authentication. This grants them complete, unmitigated control over the compromised system, leading to severe data breaches and system integrity loss.

opensshrcecriticallinux2024

Step-by-Step Mitigation Guide

To mitigate CVE-2024-6387, immediately upgrade your OpenSSH server to version 9.8p1 or newer. Verify the fix by checking the installed OpenSSH version using `ssh -V` and ensuring it's 9.8p1+. Regular patching is crucial to prevent exploitation.

  1. 1Upgrade OpenSSH to 9.8p1 or later immediately.
  2. 2Restrict SSH access via firewall: allow only trusted IPs on port 22.
  3. 3Enable fail2ban or equivalent rate-limiting to slow exploitation attempts.
  4. 4Set LoginGraceTime 0 in sshd_config as a temporary workaround (disables grace period).
  5. 5Audit SSH server logs for exploitation attempts (look for connection floods).
  6. 6Consider moving SSH to a non-standard port or VPN-only access (Tailscale, WireGuard).

Frequently Asked Questions

What is the CVSS score for CVE-2024-6387?
CVE-2024-6387 has a CVSS score of 8.1/10 (critical severity). This reflects the most severe potential impact, requiring immediate remediation.
Which versions of OpenSSH are affected?
Affected: OpenSSH 8.5p1 – 9.7p1 (glibc Linux). The vulnerability was fixed in: OpenSSH 9.8p1+.
How long does it take to fix CVE-2024-6387?
For most teams: 15–60 minutes to apply the patch, plus 15 minutes of post-patch verification. Complex multi-service environments may require 2–4 hours including staging validation.
Is CVE-2024-6387 being actively exploited?
Check the NVD entry and CISA KEV catalog for exploitation status. As a critical-severity vulnerability, treat it as a priority remediation regardless of known exploitation status.
This CVE fix guide is based on publicly available security advisories (NVD, vendor bulletins). Always test changes in a staging environment before applying to production. Verify against the official vendor advisory for the most up-to-date guidance.
🔒 Quantum-Resistant Mycelium Architecture
🛡️ 3M+ Runbooks – täglich von SecOps-Experten geprüft
🌐 Zero Known Breaches – Powered by Living Intelligence
🏛️ SOC2 & ISO 27001 Aligned • GDPR 100 % compliant
⚡ Real-Time Global Mycelium Network – 347 Bedrohungen in 60 Minuten
🧬 Trusted by SecOps Leaders worldwide