dbcve.org
Traffic ServerApplication · Apache

CVE-2023-41752

HIGH · 7.5 CVSS v3.1 Published 2023-10-17
Fix available
A fix is available. Upgrade to 8.1.9 / 9.2.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
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Traffic Server.This issue affects Apache Traffic Server: from 8.0.0 through 8.1.8, from 9.0.0 through 9.2.2. Users are recommended to upgrade to version 8.1.9 or 9.2.3, which fixes the issue.

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

Apache Traffic Server versions 8.0.0-8.1.8 and 9.0.0-9.2.2 contain an information disclosure vulnerability allowing unauthorized actors to access sensitive data. The specific nature of exposed data is not detailed in available documentation, but the HIGH CVSS score indicates significant sensitive information exposure risk.

MitigationUpgrade Apache Traffic Server to version 8.1.9 or 9.2.3. If immediate upgrade is not feasible, restrict network access to Traffic Server endpoints and review logging for indicators of exploitation.

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.9>= 9.0.0, < 9.2.3
FedoraOperating system
Affected:= 37= 38

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. Identify installed Apache Traffic Server version
    Run 'traffic_server -v' or check package manager output (e.g., 'rpm -q trafficserver' on RHEL-based systems, 'dpkg -l trafficserver' on Debian-based)
    Affected if Version is 8.0.0 through 8.1.8, or 9.0.0 through 9.2.2
  2. Confirm Fedora package version if applicable
    If running on Fedora, run 'rpm -q trafficserver' to get the exact package version and compare against CVE-affected package versions
    Affected if System is Fedora 37 or 38 with a trafficserver package version that falls within the affected range
  3. Verify network exposure of Traffic Server service
    Check if Traffic Server HTTP/S ports (default 8080, 8443) are bound to non-localhost interfaces or are accessible from untrusted networks. Review firewall rules and listen addresses in records.config
    Affected if Traffic Server endpoints are accessible from untrusted network segments without authentication barriers
  4. Review access logs for anomalous data access patterns
    Examine access logs in the logging directory for unusual or unauthorized requests that may indicate exploitation attempts, particularly to endpoints that should require authentication
    Affected if Logs show unexpected access patterns or requests from unauthorized sources to sensitive data endpoints

User is affected if their Apache Traffic Server version is 8.0.0-8.1.8 or 9.0.0-9.2.2 (or running vulnerable package on Fedora 37/38), especially if the service is network-accessible without authentication controls.

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.9 / 9.2.3 or later
Fixed in 8.1.99.2.3
Interim mitigation

Upgrade Apache Traffic Server to version 8.1.9 or 9.2.3. If immediate upgrade is not feasible, restrict network access to Traffic Server endpoints and review logging for indicators of exploitation.

Recommended fix High confidence

Upgrade to Apache Traffic Server 8.1.9 (for 8.x branch) or 9.2.3 (for 9.x branch)

  1. 1. Identify the current Apache Traffic Server version installed (e.g., using `traffic_server --version` or package manager)
  2. 2. If running version 8.0.0 through 8.1.8, plan upgrade to version 8.1.9
  3. 3. If running version 9.0.0 through 9.2.2, plan upgrade to version 9.2.3
  4. 4. Obtain the appropriate fixed version from your distribution's package repository or Apache Traffic Server official sources (https://traffic.apache.org/downloads/)
  5. 5. Upgrade the package using your system's package manager (e.g., `dnf upgrade` on Fedora, `apt-get install` on Debian)
  6. 6. After upgrade, restart the Apache Traffic Server service (e.g., `systemctl restart traffic_server` or `traffic_server -k restart`)
  7. 7. Verify the service is running and the version has been updated to the fixed release

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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