Skip to content

CVE-2024-6387

regreSSHion

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.

CVSS
8.1Highscored by the publisher (CNA)
Exploited in the wild
Not knownPublic exploit code; not in CISA KEV
EPSS
99.5%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
1 Jul 2024analysed here 12 Nov 2026

Summary

Triage

Exploitable
At runtime
Attack vector
network
Weaknesses
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

  • sonicwall:sma_6200_firmware
  • sonicwall:sma_7200_firmware
  • arista:eos
  • canonical:ubuntu_linux
  • almalinux:almalinux
  • sonicwall:sma_6210_firmware
  • sonicwall:sma_7210_firmware
  • sonicwall:sma_8200v_firmware
  • sonicwall:sra_ex_7000_firmware
  • netapp:a1k_firmware
  • netapp:a70_firmware
  • netapp:a90_firmware
  • netapp:a700s_firmware
  • netapp:8300_firmware
  • netapp:8700_firmware
  • netapp:a400_firmware
  • netapp:c400_firmware
  • netapp:a250_firmware
  • netapp:500f_firmware
  • netapp:c250_firmware
  • netapp:a800_firmware
  • netapp:c800_firmware
  • netapp:a900_firmware
  • netapp:a9500_firmware
  • netapp:c190_firmware
  • netapp:a150_firmware
  • netapp:a220_firmware
  • netapp:fas2720_firmware
  • netapp:fas2750_firmware
  • netapp:fas2820_firmware

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Yes: 1 on Exploit-DB · 97 GitHub proofs of concept
CISA SSVC
exploitation poc, automatable no, technical impact totalAssessed by CISA 2 Jul 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

GitHub proofs of concept

and 93 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 1 Jul 2024First public exploit or proof of concept
  2. 1 Jul 2024Published1 day later
  3. 2 Jul 2024CISA SSVC assessment: exploitation poc1 day later
  4. 6 Nov 2026CVE record last updated857 days (about 2 years) later
  5. 12 Nov 2026Analysed by vulneraibility.com6 days later

CVSS vector

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

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityHighNeeds specific conditions, a race or a particular configuration.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2024-6387 being exploited?

Not confirmed. CVE-2024-6387 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 100% probability of exploitation in the next 30 days.

How severe is CVE-2024-6387?

CVE-2024-6387 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2024-6387?

Yes. A fix has been recorded for CVE-2024-6387. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2024-6387 affect?

CVE-2024-6387 affects sonicwall:sma_6200_firmware, sonicwall:sma_7200_firmware, arista:eos, canonical:ubuntu_linux, and 26 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

50 references in the CVE record, grouped by the tags the record gives them.

Advisories (7)

Show 1 more

Other links (43)

Show 37 more

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com