CVE-2024-45809: Envoy is a cloud-native high-performance edge/middle/service proxy.

High CVSS 7.5

CVE id
CVE-2024-45809
Published
Last modified

Affected packages

PackageAffected versionsFixed in
Envoy
Runtimes and servers
>= 1.29.0, < 1.29.9
>= 1.30.0, < 1.30.6
>= 1.31.0, < 1.31.2
1.29.9, 1.30.6, 1.31.2

How to fix it

Upgrade Envoy to the fixed release of the line you run: 1.29.9, 1.30.6, 1.31.2.

envoy --version
  • Upgrade Envoy (the envoyproxy/envoy image tag) to the patched release.

A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.

Details

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. clearroutecache 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.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.