dbcve.org
Traffic ServerApplication · Apache

CVE-2022-28129

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/1.1 header parsing of Apache Traffic Server allows an attacker to send invalid headers. 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 · moderate confidence

Improper Input Validation vulnerability in HTTP/1.1 header parsing in Apache Traffic Server versions 8.0.0 through 9.1.2 allows remote attackers to send invalid headers, potentially leading to denial of service or other parsing-related issues.

MitigationUpgrade Apache Traffic Server to version 9.1.3 or later which contains the patch for proper input validation in HTTP/1.1 header parsing, or apply any available security patches.

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. Check if Apache Traffic Server is installed
    Run `traffic_server -V` or `traffic_ctl server start` to see if the binary exists and its version
    Affected if Apache Traffic Server is not installed on the system
  2. Determine the installed version of Apache Traffic Server
    Run `traffic_server -V` and note the version number displayed (e.g., 8.1.2, 9.0.0, 9.1.2)
    Affected if Version falls within 8.0.0 to 8.1.4 or 9.0.0 to 9.1.2 (inclusive)
  3. Verify HTTP/1.1 protocol handling is enabled
    Run `traffic_ctl config get proxy.config.http.http1_enabled` to check if HTTP/1.1 is enabled in the configuration
    Affected if HTTP/1.1 is enabled (value is 1 or true)
  4. Check if the proxy or HTTP server functionality is active
    Run `traffic_ctl server status` or check for running traffic_server processes with `ps aux | grep traffic_server`
    Affected if Apache Traffic Server is actively running and serving HTTP traffic

A system is affected if Apache Traffic Server version 8.0.0-8.1.4 or 9.0.0-9.1.2 is installed with HTTP/1.1 protocol enabled and the server is actively handling traffic.

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 patch for proper input validation in HTTP/1.1 header parsing, or apply any available security patches.

Recommended fix High confidence

Apache Traffic Server 8.1.5+ or 9.1.3+ (or latest stable 10.x release)

  1. 1. Identify the currently installed Apache Traffic Server version using: traffic_server -V or ats -V
  2. 2. For Debian 10/11 systems: Run 'apt update' and 'apt list --upgradable' to check for available package updates
  3. 3. For Fedora 35/36 systems: Run 'dnf check-update' to check for available package updates
  4. 4. Upgrade Apache Traffic Server to version 8.1.5 or later (for 8.x branch) or 9.1.3 or later (for 9.x branch)
  5. 5. On Debian: Run 'apt install trafficserver' to install the fixed package
  6. 6. On Fedora: Run 'dnf update trafficserver' to install the fixed package
  7. 7. After upgrade, restart the Traffic Server service: 'trafficctl server restart' or 'systemctl restart trafficserver'
  8. 8. Verify the new version is installed: traffic_server -V

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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