Skip to content
Noroxi
CVE-2006-5051· NVD / CVE Program· CNA redhat

Signal handler race condition in OpenSSH before 4.4 allows remote attackers to cause a denial of service (crash), and possibly execute arbit

Signal handler race condition in OpenSSH before 4.4 allows remote attackers to cause a denial of service (crash), and possibly execute arbitrary code if GSSAPI authentication is enabled, via unspecified vectors that lead to a double-free.

HighCVSS 8.1 · v3.1—Proof of concept Fix available
Published
Sep 27, 2006
Updated
Jun 16, 2026
EPSS
45.0% · 99th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

45

Plan

Add it to your regular patch cycle.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
13 / 30 · 45.0%

Affected systems

VendorProduct
openbsdopenssh
debiandebian linux
applemac os x
applemac os x server

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apple mac os xbefore 10.3.9
  • apple mac os x10.4 and later · up to 10.4.8 inclusive
  • apple mac os x serverbefore 10.3.9
  • apple mac os x server10.4 and later · up to 10.4.8 inclusive
  • debian debian linux3.1
  • openbsd opensshup to 4.4 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12opensshbefore 1:4.6p1-11:4.6p1-1
Debian:3.1opensshbefore 1:3.8.1p1-8.sarge.61:3.8.1p1-8.sarge.6
Debian:3.1openssh-krb5before 3.8.1p1-7sarge13.8.1p1-7sarge1
Debian:4.0opensshbefore 1:4.3p2-9etch31:4.3p2-9etch3
Red Hat:enterprise_linux:2.1::asopensshbefore 0:3.1p1-210:3.1p1-21
Red Hat:enterprise_linux:2.1::asopenssh-askpassbefore 0:3.1p1-210:3.1p1-21
Red Hat:enterprise_linux:2.1::asopenssh-askpass-gnomebefore 0:3.1p1-210:3.1p1-21
Red Hat:enterprise_linux:2.1::asopenssh-clientsbefore 0:3.1p1-210:3.1p1-21
Red Hat:enterprise_linux:2.1::asopenssh-serverbefore 0:3.1p1-210:3.1p1-21
Red Hat:enterprise_linux:3::asopensshbefore 0:3.6.1p2-33.30.120:3.6.1p2-33.30.12
Red Hat:enterprise_linux:3::asopenssh-askpassbefore 0:3.6.1p2-33.30.120:3.6.1p2-33.30.12
Red Hat:enterprise_linux:3::asopenssh-askpass-gnomebefore 0:3.6.1p2-33.30.120:3.6.1p2-33.30.12
Red Hat:enterprise_linux:3::asopenssh-clientsbefore 0:3.6.1p2-33.30.120:3.6.1p2-33.30.12
Red Hat:enterprise_linux:3::asopenssh-debuginfobefore 0:3.6.1p2-33.30.120:3.6.1p2-33.30.12
Red Hat:enterprise_linux:3::asopenssh-serverbefore 0:3.6.1p2-33.30.120:3.6.1p2-33.30.12
Red Hat:enterprise_linux:4::asopensshbefore 0:3.9p1-8.RHEL4.170:3.9p1-8.RHEL4.17
Red Hat:enterprise_linux:4::asopenssh-askpassbefore 0:3.9p1-8.RHEL4.170:3.9p1-8.RHEL4.17
Red Hat:enterprise_linux:4::asopenssh-askpass-gnomebefore 0:3.9p1-8.RHEL4.170:3.9p1-8.RHEL4.17
Red Hat:enterprise_linux:4::asopenssh-clientsbefore 0:3.9p1-8.RHEL4.170:3.9p1-8.RHEL4.17
Red Hat:enterprise_linux:4::asopenssh-debuginfobefore 0:3.9p1-8.RHEL4.170:3.9p1-8.RHEL4.17
Red Hat:enterprise_linux:4::asopenssh-serverbefore 0:3.9p1-8.RHEL4.170:3.9p1-8.RHEL4.17

Other highest-scoring records for the same primary product.

  • CVE-2023-38408The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if
    63This week
  • CVE-2023-25136OpenSSH server (sshd) 9.1 introduced a double-free vulnerability during options.kex_algorithms handling.
    53Plan
  • CVE-2018-15473OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after
    51Plan
  • CVE-2016-6210sshd in OpenSSH before 7.3, when SHA256 or SHA512 are used for user password hashing, uses BLOWFISH hashing on a static password when the us
    50Plan
  • CVE-2016-6515The auth_password function in auth-passwd.c in sshd in OpenSSH before 7.3 does not limit password lengths for password authentication, which
    48Plan
  • CVE-2002-0640Buffer overflow in sshd in OpenSSH 2.3.1 through 3.3 may allow remote attackers to execute arbitrary code via a large number of responses du
    48Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Debian:openssh1:4.6p1-1 · Debian:12Package registry (OSV)
Debian:openssh-krb53.8.1p1-7sarge1 · Debian:3.1Package registry (OSV)
Red Hat:openssh0:3.6.1p2-33.30.12 · Red Hat:enterprise_linux:3::asPackage registry (OSV)
Red Hat:openssh-askpass0:3.6.1p2-33.30.12 · Red Hat:enterprise_linux:3::asPackage registry (OSV)
Red Hat:openssh-askpass-gnome0:3.6.1p2-33.30.12 · Red Hat:enterprise_linux:3::asPackage registry (OSV)
Red Hat:openssh-clients0:3.6.1p2-33.30.12 · Red Hat:enterprise_linux:3::asPackage registry (OSV)
Red Hat:openssh-debuginfo0:3.6.1p2-33.30.12 · Red Hat:enterprise_linux:3::asPackage registry (OSV)
Red Hat:openssh-server0:3.6.1p2-33.30.12 · Red Hat:enterprise_linux:3::asPackage registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×3

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:352024-07-01
Proof-of-concept repository on GitHubstars:02024-07-04
Proof-of-concept repository on GitHubstars:22024-10-22

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+6486 d
  3. TodaySep 29, 2026+7307 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-415 · Double Free

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records