dbcve.org
Traffic ServerApplication · Apache

CVE-2022-32749

HIGH · 7.5 CVSS v3.1 Published 2022-12-19
Fix available
A fix is available. Upgrade to 8.1.6 / 9.1.4 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 Check for Unusual or Exceptional Conditions vulnerability handling requests in Apache Traffic Server allows an attacker to crash the server under certain conditions. This issue affects Apache Traffic Server: from 8.0.0 through 9.1.3.

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 Check for Unusual or Exceptional Conditions vulnerability in Apache Traffic Server allows remote attackers to crash the server by sending specially crafted requests that trigger an unhandled exceptional condition, resulting in denial of service.

MitigationUpgrade Apache Traffic Server to version 9.1.4 or later to patch this vulnerability. Implement rate limiting or request filtering at upstream proxies as a temporary defense if immediate upgrade is not 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.6>= 9.0.0, < 9.1.4

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. Determine installed Apache Traffic Server version
    Run 'traffic_server -V' or check the server banner via HTTP header 'Server' field, or query the management API endpoint if enabled
    Affected if Version is 8.0.0 through 8.1.5, or 9.0.0 through 9.1.3
  2. Verify ATS process is running and accessible
    Confirm the traffic_server process is active and listening on configured ports (default 8080 for proxy, 8083 for management)
    Affected if Server is running and exposed to network where attackers can send malicious requests
  3. Confirm HTTP proxy or caching features are enabled
    Check configuration files (records.config, remap.config) for enabled proxy remap rules or caching configuration
    Affected if Proxy remap rules or cache features are active, allowing external requests to reach the server

If the installed Apache Traffic Server version is 8.0.0-8.1.5 or 9.0.0-9.1.3 and the server is accessible over the network with proxy or caching features enabled, the environment is vulnerable to CVE-2022-32749.

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.6 / 9.1.4 or later
Fixed in 8.1.69.1.4
Interim mitigation

Upgrade Apache Traffic Server to version 9.1.4 or later to patch this vulnerability. Implement rate limiting or request filtering at upstream proxies as a temporary defense if immediate upgrade is not feasible.

Recommended fix High confidence

Apache Traffic Server 8.1.6 or later (for 8.x line), or 9.1.4 or later (for 9.x line)

  1. 1. Identify the currently installed Apache Traffic Server version using 'traffic_server -V' or checking package manager
  2. 2. If running version 8.0.0 through 8.1.5, plan upgrade to version 8.1.6 or later
  3. 3. If running version 9.0.0 through 9.1.3, plan upgrade to version 9.1.4 or later
  4. 4. Review release notes for the target version for any migration considerations
  5. 5. Back up configuration files in /etc/trafficserver/ or equivalent
  6. 6. Stop the Traffic Server service
  7. 7. Install the fixed version via package manager or compile from source
  8. 8. Verify the upgrade was successful by running 'traffic_server -V'
Caveat Minor version upgrades within the same major.minor line typically have minimal breaking changes; however, review release notes for any deprecation notices or configuration changes

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-32749 — 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-32749 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