CVE-2024-23323: Excessive CPU usage when URI template matcher is configured using regex in Envoy

Published Feb 9, 2024
·
Updated

Envoy is a high-performance edge/middle/service proxy. The regex expression is compiled for every request and can result in high CPU usage and increased request latency when multiple routes are configured with such matchers. This issue has been addressed in released 1.29.1, 1.28.1, 1.27.3, and 1.26.7. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Affected Software

4 affected components
Envoyproxy Envoy>=1.26.0<1.26.7
Envoyproxy Envoy>=1.27.0<1.27.3
Envoyproxy Envoy>=1.28.0<1.28.1
Envoyproxy Envoy>=1.29.0<1.29.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade envoy to a version that resolves this vulnerability.

    Fixed in 1.29.1
  2. Upgrade

    Upgrade envoy to a version that resolves this vulnerability.

    Fixed in 1.28.1
  3. Upgrade

    Upgrade envoy to a version that resolves this vulnerability.

    Fixed in 1.27.3
  4. Upgrade

    Upgrade envoy to a version that resolves this vulnerability.

    Fixed in 1.26.7

Event History

Feb 9, 2024
CVE Published
via MITRE·10:50 PM
Data Sourced
via MITRE·10:50 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-23323?

CVE-2024-23323 is considered a moderate severity vulnerability due to its impact on CPU usage and request latency.

2

How do I fix CVE-2024-23323?

To fix CVE-2024-23323, upgrade Envoy Proxy to version 1.29.1, 1.28.1, 1.27.4, or later.

3

Which versions of Envoy are affected by CVE-2024-23323?

CVE-2024-23323 affects Envoy versions between 1.26.0 and 1.26.7, 1.27.0 and 1.27.3, 1.28.0 and 1.28.1, and 1.29.0 and 1.29.1.

4

What are the implications of CVE-2024-23323?

The implications of CVE-2024-23323 include potential increased CPU usage and latency for requests depending on regex matchers in configured routes.

5

Is there a workaround for CVE-2024-23323?

Currently, the best approach for CVE-2024-23323 is to apply the recommended updates as there are no specific workarounds mentioned.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203