dbcve.org
Traffic ServerApplication · Apache

CVE-2023-33933

HIGH · 7.5 CVSS v3.1 Published 2023-06-14
Fix available
A fix is available. Upgrade to 8.1.7 / 9.2.1 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
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Software Foundation Apache Traffic Server.This issue affects Apache Traffic Server: from 8.0.0 through 9.2.0. 8.x users should upgrade to 8.1.7 or later versions 9.x users should upgrade to 9.2.1 or later versions

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 through 9.2.0 contain an information disclosure vulnerability allowing unauthorized actors to access sensitive information. This is a HIGH-severity (CVSS 7.5) vulnerability specific to the caching proxy server functionality.

MitigationUpgrade Apache Traffic Server to version 8.1.7 or later for 8.x installations, or 9.2.1 or later for 9.x installations, following standard upgrade procedures and regression testing.

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.7>= 9.0.0, < 9.2.1

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Confirm Apache Traffic Server is installed
    Run 'which traffic_server' or check for the binary at common paths like /usr/bin/traffic_server or /usr/local/bin/traffic_server. Also check package managers: 'rpm -qa | grep -i traffic' or 'dpkg -l | grep -i traffic'.
    Affected if The traffic_server binary exists on the system.
  2. Determine the installed version
    Run 'traffic_server --version' or 'traffic_ctl version' to obtain the exact version number. If these commands are unavailable, check the package version via 'rpm -q trafficserver' or 'dpkg -l trafficserver'.
    Affected if The version displayed falls within the ranges >= 8.0.0 and < 8.1.7, or >= 9.0.0 and < 9.2.1.
  3. Verify caching proxy functionality is in use
    Examine the Traffic Server configuration directory (commonly /etc/trafficserver/ or /usr/local/etc/trafficserver/). Check records.yaml for proxy.config.http.enabled set to 1, and review remap.config for active proxy mapping rules.
    Affected if The proxy.http.enabled setting is enabled or remap.config contains active forwarding rules, indicating the caching proxy feature is active.
  4. Confirm proxy service is exposed
    Check network listening status with 'ss -tlnp | grep 8080' or 'netstat -tlnp | grep 8080' (default proxy port), or review bind configuration in records.yaml under proxy.config.http.server_ports.
    Affected if The proxy port is listening and accessible, meaning the vulnerable service is exposed.

If Apache Traffic Server is running with the caching proxy enabled and the installed version is 8.0.0 through 9.2.0 (specifically < 8.1.7 or < 9.2.1), the environment is affected by CVE-2023-33933.

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.7 / 9.2.1 or later
Fixed in 8.1.79.2.1
Interim mitigation

Upgrade Apache Traffic Server to version 8.1.7 or later for 8.x installations, or 9.2.1 or later for 9.x installations, following standard upgrade procedures and regression testing.

Recommended fix High confidence

8.x -> 8.1.7 or later; 9.x -> 9.2.1 or later

  1. 1. Identify the currently installed Apache Traffic Server version using: traffic_server -V or atsversion -a
  2. 2. For 8.x versions (8.0.0 to 8.1.6): Upgrade to version 8.1.7 or later
  3. 3. For 9.x versions (9.0.0 to 9.2.0): Upgrade to version 9.2.1 or later
  4. 4. Obtain the appropriate package for your distribution from https://traffic.apache.org/downloads/ or your system's package manager
  5. 5. Install the upgraded package following standard procedures for your operating system
  6. 6. Restart the Traffic Server service: traffic_ctl server restart or systemctl restart traffic_server
  7. 7. Verify the upgrade was successful by running: traffic_server -V
Caveat Minor version upgrades typically do not introduce breaking changes; review release notes for any behavior changes

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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