Cyber Resilience

CVE-2024-6387

Race Condition in Freebsd 13.2 … 14.1

Public PoCHigh EPSSRace Condition
Published
01 July 2024
Modified
12 May 2026
Patch / advisory
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.99 99.9th percentile
Risk Priority 86 floored blend · peak EPSS

Summary

CVE-2024-6387 is a high-severity Signal Handler Race Condition (CWE-364) vulnerability in Freebsd Freebsd. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 0.1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-6387 is a security regression of the earlier CVE-2006-5051 flaw in OpenSSH's sshd server component. It stems from a race condition that allows sshd to handle certain signals unsafely during authentication, specifically when a client fails to complete authentication within a defined time window.

An unauthenticated remote attacker can trigger the race condition over the network without any credentials or user interaction. Successful exploitation can lead to arbitrary code execution with root privileges on the affected server, as reflected in the CVSS 8.1 score covering high impact to confidentiality, integrity, and availability.

Red Hat has published multiple errata (RHSA-2024:4312, RHSA-2024:4340, RHSA-2024:4389, RHSA-2024:4469, and RHSA-2024:4474) that address the issue through updated OpenSSH packages; organizations should apply these patches promptly to eliminate the regression. The EPSS score has reached 0.6579 without evidence of a material rise from a low baseline.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A 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…

more

authenticate within a set time period.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-32250Same product class: NAS / storage appliance
CVE-2023-2006Same product class: NAS / storage appliance
CVE-2023-32254Same product class: NAS / storage appliance
CVE-2024-26733Same product: Debian Debian Linux
CVE-2023-2898Same product: Debian Debian Linux
CVE-2024-26633Same product: Debian Debian Linux
CVE-2019-0211Same product: Canonical Ubuntu Linux
CVE-2023-4911Same product: Canonical Ubuntu Linux
CVE-2023-28320Same product: Apple Macos
CVE-2024-1086Same product: Debian Debian Linux

Affected Assets

sonicwall
sma 6200 firmware
all versions
sonicwall
sma 7200 firmware
all versions
arista
eos
4.32.0 — 4.32.1f
canonical
ubuntu linux
22.04, 22.10, 23.04, 23.10, 24.04
almalinux
almalinux
9.0
sonicwall
sma 6210 firmware
all versions
sonicwall
sma 7210 firmware
all versions
sonicwall
sma 8200v firmware
all versions
sonicwall
sra ex 7000 firmware
all versions
netapp
a1k firmware
all versions
+43 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V10.4.2
  • V10.4.5
  • V15.1.3
  • V15.4.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (including concurrency and fuzz testing) can discover signal-handler race conditions before deployment.

Engineering principles such as least privilege, complete mediation, and avoidance of shared mutable state in handlers directly reduce introduction of signal-handler race conditions.

Maintaining separate execution domains for each process structurally eliminates unintended concurrent access to the same shared resources.

Preventing unintended information transfer through shared system resources directly addresses the improper concurrent modification that defines a race condition.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent introduction of signal-handler race conditions during coding and review.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect signal-handler race conditions before release.

prevents

Secure SDLC practices can require avoidance of unsafe signal handling patterns.

prevents

Application security requirements can specify thread-safety and locking rules, but do not prescribe implementation details.

degrades

Secure architecture principles can mandate safe concurrency and signal design.

prevents

Secure coding standards directly prohibit race-prone signal handlers.

mitigates

Change management may catch unsafe signal code during reviews but does not address the weakness itself.

References