LiveActive security incident?Get immediate response
CVE Record

CVE-2024-6387: Openssh: regresshion - race condition in ssh allows rce/dos

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 authenticate within a set time period.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-6387 is a high-severity OpenSSH server flaw. A remote unauthenticated attacker may trigger unsafe signal handling when login times out. Successful exploitation could allow code execution or denial of service, but the source bundle shows high attack complexity and no KEV confirmation of active exploitation.

Executive priority

Prioritize remediation for externally reachable SSH services because compromise could affect confidentiality, integrity, and availability. The urgency is high, but the provided evidence supports controlled, risk-based patching rather than emergency claims of confirmed active exploitation.

Technical view

This is a regression of CVE-2006-5051 in sshd involving a race condition during signal handling. The CVSS 3.1 score is 8.1, with network attack vector, no privileges, no user interaction, and high complexity. Red Hat lists affected RHEL 9 openssh packages and OpenShift RHCOS versions.

Likely exposure

Internet-facing Linux systems running affected OpenSSH server builds are the primary concern. The provided Red Hat data specifically flags RHEL 9 variants and OpenShift Container Platform 4.13 through 4.16 RHCOS packages as affected.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. It does include public exploit-reference URLs and research coverage, so defenders should treat exposure seriously while avoiding assumptions about reliable mass exploitation.

Researcher notes

Key validation is version and package lineage, not just the OpenSSH upstream version string. Red Hat marks several older enterprise products unaffected while RHEL 9 and specific OpenShift RHCOS builds are affected, so rely on vendor advisories for platform status.

Mitigation direction

  • Apply relevant vendor updates for affected OpenSSH or platform packages.
  • Restart sshd after upgrading where vendor guidance requires it.
  • Prioritize internet-facing SSH services and administrative jump hosts.
  • Limit SSH exposure to trusted networks where operationally feasible.
  • Check Red Hat advisories for product-specific fixed package versions.

Validation and detection

  • Inventory systems exposing sshd to untrusted networks.
  • Compare installed OpenSSH packages against vendor affected and fixed versions.
  • Verify RHEL 9 and OpenShift RHCOS versions against Red Hat advisories.
  • Confirm sshd was restarted after package remediation.
  • Review security monitoring for unusual SSH authentication timeout patterns.
Prepared
Confidence
high
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-364: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-6387 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
3ADP providers
45Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9redhat

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2024-6387Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineredhat

    Reported to Red Hat.

  2. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  3. Source timelineredhat

    Made public.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorOpenSSHOpenSSH, 8.5p1unaffected
Red HatRed Hat Enterprise Linux 9openssh, 0:8.7p1-38.el9_4.1affected
Red HatRed Hat Enterprise Linux 9openssh, 0:8.7p1-38.el9_4.1affected
Red HatRed Hat Enterprise Linux 9.0 Update Services for SAP Solutionsopenssh, 0:8.7p1-12.el9_0.1affected
Red HatRed Hat Enterprise Linux 9.2 Extended Update Supportopenssh, 0:8.7p1-30.el9_2.4affected
Red HatRed Hat OpenShift Container Platform 4.13rhcos, 413.92.202407091321-0affected
Red HatRed Hat OpenShift Container Platform 4.14rhcos, 414.92.202407091253-0affected
Red HatRed Hat OpenShift Container Platform 4.15rhcos, 415.92.202407091355-0affected
Red HatRed Hat OpenShift Container Platform 4.16rhcos, 416.94.202407081958-0affected
Red HatRed Hat Ceph Storage 5opensshunaffected
Red HatRed Hat Ceph Storage 6opensshunaffected
Red HatRed Hat Ceph Storage 7opensshunaffected
Red HatRed Hat Enterprise Linux 10opensshunaffected
Red HatRed Hat Enterprise Linux 6opensshunaffected
Red HatRed Hat Enterprise Linux 7opensshunaffected
Red HatRed Hat Enterprise Linux 8opensshunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-364 · source CWE mapping

Signal Handler Race Condition

Signal Handler Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.