# CVE-2024-39920: Information disclosure in n/a

> Remote attackers can infer TCP connection content via timing side channels when clients concurrently receive slow data from attacker-controlled servers.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2024
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-796p-jr7h-8vmq

## What is CVE-2024-39920?

CVE-2024-39920 is a medium-severity vulnerability in n/a, published on 3 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The TCP protocol in RFC 9293 has a timing side channel that makes it easier for remote attackers to infer the content of one TCP connection from a client system (to any server), when that client system is concurrently obtaining TCP data at a slow rate from an attacker-controlled server, aka the "SnailLoad" issue. For example, the attack can begin by measuring RTTs via the TCP segments whose role is to provide an ACK control bit and an Acknowledgment Number.

Weakness: CWE-1255 (Comparison Logic is Vulnerable to Power Side-Channel Attacks)

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


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

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

## Is CVE-2024-39920 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-39920 is a medium-severity vulnerability in n/a, published on 3 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39920 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-39920/ (Markdown: https://insights.sbomify.com/CVE-2024-39920/index.md)
```

## Sources

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

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