dbcve.org
Traffic ServerApplication · Apache

CVE-2023-30631

HIGH · 7.5 CVSS v3.1 Published 2023-06-14
Fix available
A fix is available. Upgrade to 8.1.7 / 9.2.1 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
Improper Input Validation vulnerability in Apache Software Foundation Apache Traffic Server.  The configuration option proxy.config.http.push_method_enabled didn't function.  However, by default the PUSH method is blocked in the ip_allow configuration file.This issue affects Apache Traffic Server: from 8.0.0 through 9.2.0. 8.x users should upgrade to 8.1.7 or later versions 9.x users should upgrade to 9.2.1 or later versions

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 contains an improper input validation vulnerability where the configuration option proxy.config.http.push_method_enabled doesn't function as intended. Although the PUSH method is blocked by default in the ip_allow configuration file, the non-functional configuration option creates a scenario where proper method control cannot be enforced, potentially allowing HTTP PUSH method requests to be processed when they should be blocked.

MitigationUpgrade Apache Traffic Server to version 8.1.7 or later (for 8.x users) or 9.2.1 or later (for 9.x users) to resolve the non-functional configuration option.

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.7>= 9.0.0, < 9.2.1
Debian LinuxOperating system
Affected:= 10.0= 11.0= 12.0
FedoraOperating system
Affected:= 37= 38

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 package manager (dpkg -l traffic-server, rpm -q traffic-server) to get the installed version
    Affected if Version is >= 8.0.0 and < 8.1.7, OR >= 9.0.0 and < 9.2.1
  2. Locate traffic layout configuration
    Check records.config (typically in /etc/trafficserver/ or /usr/local/etc/trafficserver/) for proxy.config.http.push_method_enabled setting
    Affected if The push_method_enabled configuration option exists and is set to a value that suggests it should allow method control, but the ip_allow file is the only enforcement mechanism
  3. Examine ip_allow configuration for PUSH method
    Check ip_allow.config file in the same directory as records.config for PUSH method entries; default location is /etc/trafficserver/ip_allow.config
    Affected if PUSH method is explicitly allowed or not properly blocked in ip_allow.config, relying on the non-functional proxy.config.http.push_method_enabled for protection
  4. Verify if server accepts PUSH method requests
    Send a test HTTP PUSH request to the server (e.g., using curl -X PUSH) and observe the response code
    Affected if Server accepts and processes PUSH method requests when it should be blocking them based on ip_allow configuration

A user is affected if Apache Traffic Server version is 8.0.0-8.1.6 or 9.0.0-9.2.0 AND the ip_allow.config relies on the non-functional proxy.config.http.push_method_enabled option to block PUSH method requests.

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.7 / 9.2.1 or later
Fixed in 8.1.79.2.1
Interim mitigation

Upgrade Apache Traffic Server to version 8.1.7 or later (for 8.x users) or 9.2.1 or later (for 9.x users) to resolve the non-functional configuration option.

Recommended fix High confidence

8.1.7 or later for 8.x branches; 9.2.1 or later for 9.x branches

  1. 1. Identify the currently installed Apache Traffic Server version (e.g., trafficctl config get proxy.config.version.str or trafficctl server)
  2. 2. Stop the Apache Traffic Server service (e.g., systemctl stop traffic_server or trafficctl stop)
  3. 3. Upgrade Apache Traffic Server to version 8.1.7 or later for 8.x branches, or 9.2.1 or later for 9.x branches, using your system's package manager (apt, yum, dnf) or by building from source
  4. 4. Verify the new version is installed correctly (trafficctl config get proxy.config.version.str)
  5. 5. Start the Apache Traffic Server service (e.g., systemctl start traffic_server or trafficctl start)
  6. 6. Confirm the PUSH method is properly blocked by checking the ip_allow configuration file and testing the configuration option proxy.config.http.push_method_enabled

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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