# CVE-2006-5051: Race condition in n/a

> Remote attackers can cause a crash or potentially execute code via a race condition in OpenSSH, particularly when GSSAPI authentication is enabled.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-5051, GHSA-mq5h-r3rg-j9hg

## What is CVE-2006-5051?

CVE-2006-5051 is a high-severity vulnerability in Apple Mac Os X, published on 27 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2006-5051?

It affects 4 products.


Products: Apple Mac Os X, Apple Mac Os X Server, Debian Debian Linux, OpenSSH.

## How do I fix CVE-2006-5051?

Upgrade to a fixed version.

## Is CVE-2006-5051 being exploited?

There is no known exploitation of CVE-2006-5051 in the wild and no public exploit code.

Public exploit code:

- Bulk Scanning Tool for OpenSSH  CVE-2024-6387, CVE-2006-5051 , CVE-2008-4109 and others. (github_poc): https://github.com/bigb0x/CVE-2024-6387
- CVE-2024-6387, also known as RegreSSHion, is a high-severity vulnerability found in OpenSSH servers (sshd) running on glibc-based Linux systems. It is a regression of a previously fixed vulnerability (CVE-2006-5051), which means the issue was reintroduced in newer versions of OpenSSH. (github_poc): https://github.com/anhvutuan/CVE-2024-6387-poc-1
- A security regression (CVE-2006-5051) was discovered in OpenSSH's server (sshd). There is a race condition which can lead to 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. (github_poc): https://github.com/sardine-web/CVE-2024-6387_Check

## Other vulnerabilities in Apple Mac Os X

- [CVE-2014-7169](https://insights.sbomify.com/CVE-2014-7169/): GNU Bourne-Again Shell (Bash) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2014-6271](https://insights.sbomify.com/CVE-2014-6271/): GNU Bourne-Again Shell (Bash) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2012-1823](https://insights.sbomify.com/CVE-2012-1823/): PHP-CGI Query String Parameter (critical 9.8, exploited in the wild)
- [CVE-2021-30713](https://insights.sbomify.com/CVE-2021-30713/): Apple macOS Unspecified (high 7.8, exploited in the wild)
- [CVE-2019-8526](https://insights.sbomify.com/CVE-2019-8526/): Apple macOS Use-After-Free (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-5051 and fix it if it is affected.

What it is: CVE-2006-5051 is a high-severity vulnerability in Apple Mac Os X, published on 27 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-5051 in the wild and no public exploit code.

Affected product: Apple Mac Os X. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-5051/ (Markdown: https://insights.sbomify.com/CVE-2006-5051/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-5051
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-5051
- OSV: https://osv.dev/vulnerability/CVE-2006-5051

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-5051/
Summaries are generated and may contain mistakes; the official description above is the record.