dbcve.org
Traffic ServerApplication · Apache

CVE-2022-25763

HIGH · 7.5 CVSS v3.1 Published 2022-08-10
Fix available
A fix is available. Upgrade to 8.1.5 / 9.1.3 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 request validation of Apache Traffic Server allows an attacker to create smuggle or cache poison attacks. 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 request parsing allows attackers to craft malicious requests that can smuggle requests through the proxy or poison cached responses. This exploits weaknesses in how HTTP/2 request headers and frames are validated against the protocol specification.

MitigationUpgrade Apache Traffic Server to version 9.1.3 or later which contains the proper input validation fix for HTTP/2 request handling.

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.5>= 9.0.0, < 9.1.3
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. Identify Apache Traffic Server version
    Run 'traffic_server --version' or 'traffic_ctl config get version' to retrieve the installed Apache Traffic Server version number
    Affected if Version is >= 8.0.0 and < 8.1.5, OR >= 9.0.0 and < 9.1.3
  2. Confirm HTTP/2 protocol support is enabled
    Check the configuration file (records.config) for proxy.config.http2.enabled variable, or inspect TLS/ssl.config for HTTP/2 ALPN negotiation settings
    Affected if HTTP/2 is explicitly enabled in the Traffic Server configuration (value set to 1 or true)
  3. Verify HTTP/2 is exposed to untrusted clients
    Review proxy.config.http2.max_concurrent_streams and listener bind addresses in records.config to confirm HTTP/2 connections are accepted from external clients
    Affected if HTTP/2 listener ports are bound to non-localhost interfaces accessible to untrusted network traffic
  4. Check operating system package version (Debian/Fedora)
    On Debian run 'dpkg -l | grep traffic-server'; on Fedora run 'rpm -qa | grep traffic-server' to get the OS-packaged version
    Affected if Package version corresponds to Debian 11.0, Fedora 35, or Fedora 36 with vulnerable Apache Traffic Server version

Environment is affected if Apache Traffic Server version is in the vulnerable ranges (8.0.0-8.1.4 or 9.0.0-9.1.2) AND HTTP/2 protocol support is enabled and accessible to potential attackers.

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.5 / 9.1.3 or later
Fixed in 8.1.59.1.3
Interim mitigation

Upgrade Apache Traffic Server to version 9.1.3 or later which contains the proper input validation fix for HTTP/2 request handling.

Recommended fix High confidence

Apache Traffic Server 8.1.5 or 9.1.3 (depending on current branch)

  1. Upgrade Apache Traffic Server 8.0.0-8.1.4 to version 8.1.5
  2. Upgrade Apache Traffic Server 9.0.0-9.1.2 to version 9.1.3
  3. For Debian 11.0 systems, apply the Debian security update package when available via: apt update && apt upgrade trafficserver
  4. For Fedora 35 and 36 systems, apply the Fedora security update when available via: dnf update trafficserver

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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