# CVE-2024-53270: HTTP/1: sending overload crashes when the request is reset beforehand in envoy

> A null pointer dereference in Envoy proxy causes a crash when handling overloaded HTTP/1 requests that are reset prematurely, requiring specific load shedding configuration.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 18 Dec 2024
- **Updated:** 18 Dec 2024
- **Also known as:** BIT-envoy-2024-53270, GHSA-q9qv-8j52-77p3

## What is CVE-2024-53270?

CVE-2024-53270 is a high-severity vulnerability in Envoyproxy Envoy, published on 18 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Envoy is a cloud-native high-performance edge/middle/service proxy. In affected versions `sendOverloadError` is going to assume the active request exists when `envoy.load_shed_points.http1_server_abort_dispatch` is configured. If `active_request` is nullptr, only onMessageBeginImpl() is called. However, the `onMessageBeginImpl` will directly return ok status if the stream is already reset leading to the nullptr reference. The downstream reset can actually happen during the H/2 upstream reset. As a result envoy may crash. This issue has been addressed in releases 1.32.3, 1.31.5, 1.30.9, and 1.29.12. Users are advised to upgrade. Users unable to upgrade may disable `http1_server_abort_dispatch` load shed point and/or use a high threshold.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-670 (Always-Incorrect Control Flow Implementation)

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

1 open source package ship an affected version, including envoy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `envoy` | Bitnami | All versions | 1.29.12, 1.30.9, 1.31.5, 1.32.3 |

Products: Envoyproxy Envoy.

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

Upgrade envoy to a fixed version for your release line: 1.29.12, 1.30.9, 1.31.5 or 1.32.3.

## Is CVE-2024-53270 being exploited?

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

## Other vulnerabilities in Envoyproxy Envoy

- [CVE-2022-29226](https://insights.sbomify.com/CVE-2022-29226/): Trivial authentication bypass in Envoy (critical 10.0)
- [CVE-2019-18801](https://insights.sbomify.com/CVE-2019-18801/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-18802](https://insights.sbomify.com/CVE-2019-18802/): Security feature bypass in n/a (critical 9.8)
- [CVE-2020-35470](https://insights.sbomify.com/CVE-2020-35470/): Information disclosure in n/a (high 8.8)
- [CVE-2024-23324](https://insights.sbomify.com/CVE-2024-23324/): Envoy ext auth can be bypassed when Proxy protocol filter sets invalid UTF-8 metadata (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53270 is a high-severity vulnerability in Envoyproxy Envoy, published on 18 Dec 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-53270 exists.

Affected packages and fixed versions:
- envoy (Bitnami): affected all versions; fixed in 1.29.12, 1.30.9, 1.31.5, 1.32.3

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

## Sources

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

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