dbcve.org
Traffic ServerApplication · Apache

CVE-2022-31780

HIGH · 7.5 CVSS v3.1 Published 2022-08-10
Fix available
A fix is available. Upgrade to after 9.1.2 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 HTTP/2 frame handling of Apache Traffic Server allows an attacker to smuggle requests. This issue affects Apache Traffic Server 8.0.0 to 9.1.2.

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 to 9.1.2 contain an improper input validation vulnerability in HTTP/2 frame handling that enables HTTP request smuggling. The vulnerability allows attackers to bypass security controls by crafting malicious HTTP/2 frames that can be interpreted as separate requests, potentially leading to cache poisoning or unauthorized access to protected resources.

MitigationUpgrade Apache Traffic Server to version 9.1.3 or later which contains the fix for this vulnerability. If immediate upgrading is not possible, consider disabling HTTP/2 or implementing additional request validation at upstream proxies.

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.4>= 9.0.0, <= 9.1.2
Debian LinuxOperating system
Affected:= 10.0= 11.0
FedoraOperating system
Affected:= 35= 36

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 and version
    Run 'traffic_server -V' or check package manager (dpkg -l | grep traffic, rpm -qa | grep traffic) to find the installed version
    Affected if Version is >= 8.0.0 and <= 8.1.4, OR >= 9.0.0 and <= 9.1.2
  2. Confirm HTTP/2 protocol is enabled
    Inspect the Traffic Server configuration file (records.config or remap.config) for 'proxy.config.http.enable_http2' set to 1, or check if any remap rules explicitly enable HTTP/2
    Affected if HTTP/2 is enabled (value set to 1 or enabled in remap config)
  3. Review access logs for HTTP/2 request smuggling patterns
    Examine traffic_server access logs (access.log) for abnormal request patterns, such as multiple requests encoded within single HTTP/2 frames, or requests with mismatched Content-Length and Transfer-Encoding headers
    Affected if Logs show anomalous HTTP/2 requests with inconsistent header parsing or unexpected request boundaries

If Apache Traffic Server version falls within 8.0.0-8.1.4 or 9.0.0-9.1.2 AND HTTP/2 is enabled, the environment is potentially affected by this request smuggling vulnerability.

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 a release after 9.1.2
Interim mitigation

Upgrade Apache Traffic Server to version 9.1.3 or later which contains the fix for this vulnerability. If immediate upgrading is not possible, consider disabling HTTP/2 or implementing additional request validation at upstream proxies.

Recommended fix High confidence

Apache Traffic Server 9.2.0 or later

  1. 1. Back up your current Apache Traffic Server configuration and data directory before upgrading.
  2. 2. For Debian systems (10.0, 11.0): Run 'apt-get update' and 'apt-get install trafficserver' to install the latest available fixed version from Debian repositories, or upgrade to Debian 12 which ships with a fixed version.
  3. 3. For Fedora systems (35, 36): Run 'dnf update trafficserver' to install the latest security patches containing the fixed version.
  4. 4. For Apache Traffic Server direct installations: Download and install version 9.2.0 or later from the Apache Traffic Server project (https://trafficserver.apache.org/downloads).
  5. 5. After upgrading, restart the Traffic Server service using 'traffic_ctl server restart' or your system's service manager.
  6. 6. Verify the upgrade by checking the Traffic Server version with 'traffic_ctl version' and confirm HTTP/2 functionality is working correctly.
Caveat Review the release notes for 9.2.0 for any configuration or API changes; minor version upgrades typically have minimal breaking changes but HTTP/2 behavior may have been adjusted

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
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
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,840.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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