# CVE-2024-39223: Missing key verification in gost

> Attackers can bypass SSH authentication and intercept communications if the HostKeyCallback is configured to ignore host keys.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** 3 Jul 2024
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-8wxx-35qc-vp6r, GO-2024-3224, UBUNTU-CVE-2024-39223

## What is CVE-2024-39223?

CVE-2024-39223 is a critical authentication bypass vulnerability in n/a, published on 3 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass in the SSH service of gost v2.11.5 allows attackers to intercept communications via setting the HostKeyCallback function to ssh.InsecureIgnoreHostKey

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2024-39223?

3 open source packages ship an affected version, including github.com/ginuerzh/gost.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ginuerzh/gost` | Go | All versions | None |
| `github.com/ginuerzh/gost` | Go | All versions to 2.11.5 | None |
| `github.com/ginuerzh/gost` | Go | All versions to 2.11.5 | None |

## How do I fix CVE-2024-39223?

Apply the vendor's patch.

## Is CVE-2024-39223 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-39223 and fix it if it is affected.

What it is: CVE-2024-39223 is a critical authentication bypass vulnerability in n/a, published on 3 Jul 2024. 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-2024-39223 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/ginuerzh/gost (Go): affected all versions; no fix listed
- github.com/ginuerzh/gost (Go): affected all versions up to 2.11.5; no fix listed
- github.com/ginuerzh/gost (Go): affected all versions up to 2.11.5; no fix listed

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-2024-39223/ (Markdown: https://insights.sbomify.com/CVE-2024-39223/index.md)
```

## Sources

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

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