CVE-2024-6387
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security regression (CVE-2006-5051) was discovered in OpenSSH's server (sshd). There is a race condition which can lead sshd to handle some signals in an unsafe manner. An unauthenticated, remote attacker may be able to trigger it by failing to authenticate within a set time period.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisA detailed technical summary for this CVE is being prepared.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 23.10= 24.04= 22.04= 22.10= 23.04= 4.0= 9.0= 9.4= 9.0_aarch64= 9.4_aarch64= 9.0_s390x= 9.4_s390xCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to OpenSSH version 9.8p1 or later, which contains the fix for CVE-2024-6387. For Ubuntu, upgrade to Ubuntu 24.04 LTS or apply updates to openssh-server package. For RHEL 9.x, ensure openssh-9.0p1 or later is installed.
- 1. Identify the current OpenSSH version by running: sshd -V or rpm -q openssh-server (RHEL) / dpkg -l openssh-server (Ubuntu)
- 2. For Ubuntu systems: Run 'sudo apt update' followed by 'sudo apt upgrade openssh-server' to obtain the latest security patches
- 3. For RHEL/Enterprise Linux systems: Run 'sudo yum update openssh-server' or 'sudo dnf update openssh-server' to apply security fixes
- 4. After updating, verify the new version is installed: rpm -q openssh-server (RHEL) / dpkg -l openssh-server (Ubuntu)
- 5. Restart the sshd service to load the updated binary: 'sudo systemctl restart sshd' (Ubuntu) or 'sudo systemctl restart sshd' (RHEL)
- 6. Verify sshd is running correctly: 'sudo systemctl status sshd'
- 7. Test SSH connectivity from a remote client to confirm the service operates normally after the update
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6387 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- www.openwall.com
- santandersecurityresearch.github.io
- www.openwall.com
- github.com
- lists.mindrot.org
- news.ycombinator.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- bugzilla.redhat.com
- santandersecurityresearch.github.io
- www.openssh.com
- www.qualys.com
- archlinux.org
- arstechnica.com
- blog.qualys.com
- explore.alas.aws.amazon.com
- github.com
- lists.almalinux.org
- psirt.global.sonicwall.com
- security-tracker.debian.org
- security.netapp.com
- sig-security.rocky.page
- stackdiary.com
- support.apple.com
- support.apple.com
- support.apple.com
- ubuntu.com
- ubuntu.com
- www.akamai.com
- www.arista.com
- www.freebsd.org
- www.splunk.com
- www.suse.com
- www.theregister.com
- www.vicarius.io
- ftp.netbsd.org
- lists.mindrot.org
- forum.vmssoftware.com
- github.com
- github.com
- github.com
- github.com
- github.com
- github.com
- github.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.exploit-db.com
- seclists.org
- seclists.org
- seclists.org
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- packetstorm.news
- cert-portal.siemens.com
- cert-portal.siemens.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-6387 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data