dbcve.org
EnvoyApplication · Envoyproxy

CVE-2024-45809

HIGH · 7.5 CVSS v3.1 Published 2024-09-20
Fix available
A fix is available. Upgrade to 1.29.9 / 1.30.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Envoy's JWT filter can crash when remote JWKs are used with clear_route_cache enabled and header operations modify requests to not match any route. The issue stems from incorrect ordering of continueDecoding and clearRouteCache, causing a nullptr reference conversion from route().

MitigationUpgrade Envoy to versions 1.31.2, 1.30.6, or 1.29.9. There are no available workarounds for this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EnvoyApplication
Affected:>= 1.29.0, < 1.29.9>= 1.30.0, < 1.30.6>= 1.31.0, < 1.31.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Envoy version
    Run envoy --version or look at the Envoy binary/version file to identify the installed version
    Affected if The version falls within >=1.29.0,<1.29.9 OR >=1.30.0,<1.30.6 OR >=1.31.0,<1.31.2
  2. Verify JWT authentication filter is enabled
    Inspect Envoy configuration (static_resources > filters) or dynamic configuration for presence of envoy.filters.http.jwt_authn filter
    Affected if JWT authentication filter is not present in the configuration
  3. Confirm remote JWKs are configured
    Review JWT filter config for remote_jwks section (http_uri cluster references) versus inline_jwks or local_jwks
    Affected if Remote JWKs are not configured - only local/inline JWKs are used
  4. Check if clear_route_cache is enabled
    Review JWT filter provider or rule configuration for clear_route_cache: true setting
    Affected if clear_route_cache is not set to true in the JWT filter configuration
  5. Verify header operations modify request routing
    Review JWT filter config for on_forward_headers or other header manipulation that could change request path/headers to not match any route (such as header_to_modify or header manipulations in rules)
    Affected if No header operations are configured that would cause the modified request to not match any route (which would trigger the clear_route_cache path)

A user is affected only if running an affected Envoy version AND using JWT filter with remote JWKs AND clear_route_cache enabled AND header operations that can modify requests to no longer match any route.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.29.9 / 1.30.6 / 1.31.2 or later
Fixed in 1.29.91.30.61.31.2
Interim mitigation

Upgrade Envoy to versions 1.31.2, 1.30.6, or 1.29.9. There are no available workarounds for this vulnerability.

Recommended fix High confidence

1.31.2 (or 1.30.6 for 1.30.x, or 1.29.9 for 1.29.x)

  1. 1. Identify the currently running Envoy version in your environment
  2. 2. For Envoy 1.29.x: Upgrade to version 1.29.9
  3. 3. For Envoy 1.30.x: Upgrade to version 1.30.6
  4. 4. For Envoy 1.31.x: Upgrade to version 1.31.2
  5. 5. If running an older version (below 1.29.0), upgrade to one of the specified fixed versions
  6. 6. Test the upgrade in a non-production environment to verify the fix resolves the crash issue
  7. 7. Deploy the upgraded version to production
Caveat Point releases typically do not introduce breaking changes; review Envoy release notes for any minor behavioral changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Envoy Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45809 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45809 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data