dbcve.org
Traffic ServerApplication · Apache

CVE-2022-31779

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 header parsing 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

Improper input validation in Apache Traffic Server's HTTP/2 header parsing allows attackers to smuggle requests by manipulating HTTP/2 headers in ways the front-end and back-end interpret differently, bypassing security controls.

MitigationUpgrade Apache Traffic Server to version 9.1.3 or later to patch the vulnerability; alternatively, disable HTTP/2 if upgrading is not immediately feasible.

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:= 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. Determine installed Apache Traffic Server version
    Run 'traffic_server --version' from command line, or check via package manager: 'dpkg -l | grep traffic-server' on Debian/Ubuntu, 'rpm -qi trafficserver' on RHEL/Fedora
    Affected if Version is 8.0.0 through 8.1.4, or 9.0.0 through 9.1.2 (these are the vulnerable ranges)
  2. Verify HTTP/2 protocol is enabled in configuration
    Inspect the Traffic Server records.config file (typically in /etc/trafficserver/) and search for 'proxy.config.http2.enabled' - check if set to integer value 1
    Affected if HTTP/2 is enabled (proxy.config.http2.enabled is set to 1)
  3. Confirm HTTP/2 inbound connections are accepted
    Check for any 'http2' entries in records.config under 'CONFIG proxy.config.http2' or review SSL/TLS configuration files where HTTP/2 protocol negotiation may be configured
    Affected if HTTP/2 is listed as an accepted protocol in the server configuration

Your environment is affected only if the installed Apache Traffic Server version falls within 8.0.0-8.1.4 or 9.0.0-9.1.2 AND HTTP/2 protocol support is actively enabled in the configuration

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.

From vendor data
Upgrade available Upgrade to a release after 9.1.2
Interim mitigation

Upgrade Apache Traffic Server to version 9.1.3 or later to patch the vulnerability; alternatively, disable HTTP/2 if upgrading is not immediately feasible.

Fix this in Traffic Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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