# CVE-2024-22590: Other in n/a

> The Kwik TLS engine fails to track connection state, allowing attackers to overwrite Client Hello messages even after establishment, bypassing TLS security mechanisms.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** No
- **Published:** 28 May 2024
- **Updated:** 13 Feb 2025

## What is CVE-2024-22590?

CVE-2024-22590 is a critical vulnerability in n/a, published on 28 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The TLS engine in Kwik commit 745fd4e2 does not track the current state of the connection. This vulnerability can allow Client Hello messages to be overwritten at any time, including after a connection has been established.

Weakness: CWE-372 (Incomplete Internal State Distinction)

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


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

No fix has been published for CVE-2024-22590 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-22590 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22590 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22590 is a critical vulnerability in n/a, published on 28 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22590 exists.

Affected product: n/a. 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-2024-22590/ (Markdown: https://insights.sbomify.com/CVE-2024-22590/index.md)
```

## Sources

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

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