# CVE-2024-45809: Jwt filter crash in the clear route cache with remote JWKs in envoy

> A null pointer dereference in Envoy's JWT filter causes a crash when specific routing and header configurations are used with remote JWKs.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Sep 2024
- **Updated:** 20 Sep 2024
- **Also known as:** BIT-envoy-2024-45809, GHSA-wqr5-qmq7-3qw3

## What is CVE-2024-45809?

CVE-2024-45809 is a medium-severity vulnerability in Envoyproxy Envoy, published on 19 Sep 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Envoy is a cloud-native high-performance edge/middle/service proxy. Jwt filter will lead to an Envoy crash when clear route cache with remote JWKs. In the following case: 1. remote JWKs are used, which requires async header processing; 2. clear_route_cache is enabled on the provider; 3. header operations are enabled in JWT filter, e.g. header to claims feature; 4. the routing table is configured in a way that the JWT header operations modify requests to not match any route. When these conditions are met, a crash is triggered in the upstream code due to nullptr reference conversion from route(). The root cause is the ordering of continueDecoding and clearRouteCache. This issue has been addressed in versions 1.31.2, 1.30.6, and 1.29.9. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `envoy` | Bitnami | From 1.29.0 | 1.29.9, 1.30.6, 1.31.2 |

Products: Envoyproxy Envoy.

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

Upgrade envoy to a fixed version for your release line: 1.29.9, 1.30.6 or 1.31.2.

## Is CVE-2024-45809 being exploited?

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

## 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-45809 and fix it if it is affected.

What it is: CVE-2024-45809 is a medium-severity vulnerability in Envoyproxy Envoy, published on 19 Sep 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-45809 in the wild and no public exploit code.

Affected packages and fixed versions:
- envoy (Bitnami): affected from 1.29.0; fixed in 1.29.9, 1.30.6, 1.31.2

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

## Sources

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

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