dbcve.org
Traffic ServerApplication · Apache

CVE-2024-35161

HIGH · 7.5 CVSS v3.1 Published 2024-07-26
Fix available
A fix is available. Upgrade to 8.1.11 / 9.2.5 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
Apache Traffic Server forwards malformed HTTP chunked trailer section to origin servers. This can be utilized for request smuggling and may also lead cache poisoning if the origin servers are vulnerable. This issue affects Apache Traffic Server: from 8.0.0 through 8.1.10, from 9.0.0 through 9.2.4. Users can set a new setting (proxy.config.http.drop_chunked_trailers) not to forward chunked trailer section. Users are recommended to upgrade to version 8.1.11 or 9.2.5, which fixes the issue.

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

Apache Traffic Server improperly forwards malformed HTTP chunked trailer sections to origin servers. This allows attackers to perform HTTP request smuggling by manipulating trailer boundaries, potentially poisoning caches if origin servers have parsing vulnerabilities.

MitigationUpgrade to Apache Traffic Server 8.1.11 or 9.2.5, or enable the proxy.config.http.drop_chunked_trailers setting to prevent forwarding of chunked trailer sections.

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
Traffic ServerApplication
Affected:>= 8.0.0, < 8.1.11>= 9.0.0, < 9.2.5

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
High
Availability
None

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

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. Identify Apache Traffic Server installation
    Run 'traffic_server -v' or check package manager for installed 'trafficserver' package
    Affected if Apache Traffic Server is not installed
  2. Determine installed version
    Execute 'traffic_server -v' to get version output, or 'rpm -q trafficserver' / 'dpkg -l trafficserver'
    Affected if Version is >= 8.0.0 and < 8.1.11, OR >= 9.0.0 and < 9.2.5
  3. Verify mitigation setting is not enabled
    Query the configuration using 'traffic_ctl config get proxy.config.http.drop_chunked_trailers' or check records.config for this setting
    Affected if Setting value is 0 or not present (default), meaning trailers are being forwarded
  4. Confirm proxy mode forwards to origins
    Check if proxy.config.reverse_proxy.enabled or proxy.config.http.forward_connect_enabled is set to 1, or review traffic_server's role in your deployment
    Affected if Server acts as a proxy forwarding requests to origin servers

You are affected if Apache Traffic Server version falls within the vulnerable ranges AND the drop_chunked_trailers setting is not enabled AND the server forwards chunked HTTP traffic to origin servers.

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 8.1.11 / 9.2.5 or later
Fixed in 8.1.119.2.5
Interim mitigation

Upgrade to Apache Traffic Server 8.1.11 or 9.2.5, or enable the proxy.config.http.drop_chunked_trailers setting to prevent forwarding of chunked trailer sections.

Recommended fix High confidence

8.1.11 (for 8.x versions) or 9.2.5 (for 9.x versions)

  1. 1. Identify current Apache Traffic Server version by running: traffic_server -v or ats -v
  2. 2. Back up all Traffic Server configuration files (located typically in /etc/trafficserver/ or /usr/local/etc/trafficserver/)
  3. 3. If running version 8.0.0 through 8.1.10: upgrade to version 8.1.11 or later
  4. 4. If running version 9.0.0 through 9.2.4: upgrade to version 9.2.5 or later
  5. 5. Obtain the upgrade from the official Apache Traffic Server downloads page: https://traffic.apache.org/download/
  6. 6. Install the new package using your system's package manager (e.g., apt, yum, dnf) or compile from source
  7. 7. Verify the new version is installed: traffic_server -v
  8. 8. Restart the Traffic Server service: traffic_ctl restart or systemctl restart trafficserver
Caveat Minor patch releases typically have no breaking changes; test existing configurations after upgrade

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

Fix this in Traffic Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,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 $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35161 — 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-35161 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