# CVE-2024-2758: CVE-2024-2758

> Tempesta FW rate limits are misconfigured by default, allowing attackers to cause denial of service via empty CONTINUATION frames.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-5x2g-c9gv-xwq2

## What is CVE-2024-2758?

CVE-2024-2758 is a medium-severity denial of service vulnerability in Tempesta FW, published on 3 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Tempesta FW rate limits are not enabled by default. They are either set too large to capture empty CONTINUATION frames attacks or too small to handle normal HTTP requests appropriately.

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


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

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

## Is CVE-2024-2758 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2758 is a medium-severity denial of service vulnerability in Tempesta FW, published on 3 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-2758 in the wild and no public exploit code.

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

## Sources

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

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