CVE-2024-35296: Apache Traffic Server: Invalid Accept-Encoding can force forwarding requests

Published Jul 26, 2024
·
Updated

Invalid Accept-Encoding header can cause Apache Traffic Server to fail cache lookup and force forwarding requests.

This issue affects Apache Traffic Server: from 8.0.0 through 8.1.10, from 9.0.0 through 9.2.4.

Users are recommended to upgrade to version 8.1.11 or 9.2.5, which fixes the issue.

Affected Software

4 affected componentsFixes available
Apache Traffic Server>=8.0.0<8.1.11
Apache Traffic Server>=9.0.0<9.2.5
debian/trafficserver<9.2.5+ds-0+deb12u1
9.2.5+ds-0+deb12u1
debian/trafficserver
9.2.5+ds-0+deb12u4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/trafficserver to a version that resolves this vulnerability.

    Fixed in 9.2.5+ds-0+deb12u1
  2. Upgrade

    Upgrade debian/trafficserver to a version that resolves this vulnerability.

    Fixed in 9.2.5+ds-0+deb12u4
  3. Upgrade

    Upgrade Apache Traffic Server to a version that resolves this vulnerability.

    Fixed in 8.1.11
  4. Upgrade

    Upgrade Apache Traffic Server to a version that resolves this vulnerability.

    Fixed in 9.2.5

Event History

Jul 26, 2024
CVE Published
via MITRE·09:11 AM
Data Sourced
via MITRE·09:11 AM
DescriptionWeakness
Data Sourced
via NVD·10:15 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·10:15 AM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2024-35296?

CVE-2024-35296 has a moderate severity level, as it can cause cache lookup failures in Apache Traffic Server.

2

How do I fix CVE-2024-35296?

To fix CVE-2024-35296, upgrade Apache Traffic Server to version 8.1.11 or 9.2.5.

3

What versions of Apache Traffic Server are affected by CVE-2024-35296?

CVE-2024-35296 affects Apache Traffic Server versions from 8.0.0 to 8.1.10 and from 9.0.0 to 9.2.4.

4

What consequences can arise from not addressing CVE-2024-35296?

Failing to address CVE-2024-35296 may result in improper request forwarding and inefficiencies in cache management.

5

Is there a workaround for CVE-2024-35296 if I cannot upgrade?

There are no officially recommended workarounds for CVE-2024-35296; upgrading is advised.

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