dbcve.org
Traffic ServerApplication · Apache

CVE-2024-31309

HIGH · 7.5 CVSS v3.1 Published 2024-04-10
Fix available
A fix is available. Upgrade to 8.1.10 / 9.2.4 or later.
See remediation →
84/100
Remediation priority · High
High EPSS 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
HTTP/2 CONTINUATION DoS attack can cause Apache Traffic Server to consume more resources on the server.  Version from 8.0.0 through 8.1.9, from 9.0.0 through 9.2.3 are affected. Users can set a new setting (proxy.config.http2.max_continuation_frames_per_minute) to limit the number of CONTINUATION frames per minute.  ATS does have a fixed amount of memory a request can use and ATS adheres to these limits in previous releases. Users are recommended to upgrade to versions 8.1.10 or 9.2.4 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 versions 8.0.0-8.1.9 and 9.0.0-9.2.3 are vulnerable to an HTTP/2 CONTINUATION frame DoS attack that can cause excessive resource consumption. The vulnerability stems from the lack of rate limiting on CONTINUATION frames, allowing an attacker to overwhelm server resources.

MitigationUpgrade to version 8.1.10 or 9.2.4, or configure proxy.config.http2.max_continuation_frames_per_minute to limit CONTINUATION frames per minute.

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.10>= 9.0.0, < 9.2.4
Debian LinuxOperating system
Affected:= 10.0
FedoraOperating system
Affected:= 38= 39= 40

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. Identify Apache Traffic Server version
    Run 'traffic_server -v' or check the package version using your system package manager (e.g., 'dpkg -l | grep traffic-server' on Debian, 'rpm -qi trafficserver' on Fedora/RHEL)
    Affected if The installed version is 8.0.0 through 8.1.9, or 9.0.0 through 9.2.3
  2. Verify HTTP/2 protocol support is enabled
    Check the records.config or equivalent configuration file for 'proxy.config.http2.enabled' or inspect the running configuration using 'traffic_ctl config get proxy.config.http2.enabled'
    Affected if HTTP/2 is enabled (value set to 1 or true) - the vulnerability only applies when HTTP/2 traffic is accepted
  3. Check CONTINUATION frame rate limit setting
    Query the configuration using 'traffic_ctl config get proxy.config.http2.max_continuation_frames_per_minute' or inspect records.config for this setting
    Affected if The setting is not defined, commented out, or set to 0 (unlimited) - meaning the server has no protection against CONTINUATION frame flooding

The environment is affected if the installed Apache Traffic Server version falls within 8.0.0-8.1.9 or 9.0.0-9.2.3, HTTP/2 is enabled, and no rate limit is configured for CONTINUATION frames per minute.

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.10 / 9.2.4 or later
Fixed in 8.1.109.2.4
Interim mitigation

Upgrade to version 8.1.10 or 9.2.4, or configure proxy.config.http2.max_continuation_frames_per_minute to limit CONTINUATION frames per minute.

Recommended fix High confidence

Upgrade to Apache Traffic Server 8.1.10 (for 8.x branch) or 9.2.4 (for 9.x branch)

  1. 1. Identify the currently installed Apache Traffic Server version using: traffic_server --version or atsversion
  2. 2. If running version 8.0.0 through 8.1.9, plan upgrade to version 8.1.10
  3. 3. If running version 9.0.0 through 9.2.3, plan upgrade to version 9.2.4
  4. 4. Download the appropriate fixed release from https://archive.apache.org/dist/trafficserver/
  5. 5. Back up the current Traffic Server configuration and data directories
  6. 6. Stop the Traffic Server service: traffic_ctl server stop
  7. 7. Install the new version using the package manager or compile from source
  8. 8. Start the Traffic Server service: traffic_ctl server start
Caveat Review release notes for any configuration or API changes between versions; test in staging environment before production deployment

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

Fix this in Traffic Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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