Traffic ServerApplication · Apache
CVE-2022-47184
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Software Foundation Apache Traffic Server.This issue affects Apache Traffic Server: 8.0.0 to 9.2.0.
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 confidenceApache Traffic Server versions 8.0.0 through 9.2.0 contain an information disclosure vulnerability allowing unauthorized actors to access sensitive information. The vulnerability is network-exploitable and rated HIGH severity due to the potential exposure of sensitive data.
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
>= 8.0.0, < 8.1.7>= 9.0.0, < 9.2.1
Debian LinuxOperating system
= 11.0= 12.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Traffic Server versionRun 'traffic_server --version' or 'ats -version' to get the installed version numberAffected if Version output is empty or not found, indicating Traffic Server may not be installed
-
Compare version against vulnerability rangesCompare the installed version to the affected ranges: >= 8.0.0 and < 8.1.7, OR >= 9.0.0 and < 9.2.1Affected if Installed version falls within either 8.0.0-8.1.6 or 9.0.0-9.2.0
-
Check Debian package version if applicableOn Debian systems, run 'dpkg -l | grep traffic-server' or 'apt list --installed | grep traffic-server'Affected if Running Debian 11 or 12 with Apache Traffic Server package installed in an affected version
-
Verify network exposureCheck if Traffic Server is bound to a network interface and accessible remotely. Review configuration files (records.config, remap.config) and running process bindings using 'netstat -tlnp | grep traffic' or 'ss -tlnp | grep traffic'Affected if Service is network-accessible from untrusted networks, as the vulnerability is network-exploitable
User is affected if Apache Traffic Server version is 8.0.0-8.1.6, 9.0.0-9.2.0, or matching Debian package versions on Debian 11/12, AND the service is network accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.1.79.2.1
Upgrade Apache Traffic Server to version 9.2.1 or later to patch the vulnerability, or apply the specific security patch if available from Apache.
Apache Traffic Server 8.1.7 or 9.2.1 (depending on your current major version)
- Upgrade Apache Traffic Server to version 8.1.7 or later for the 8.x line
- Alternatively, upgrade to version 9.2.1 or later for the 9.x line
- If using Debian, apply the latest Debian security updates for the traffic-server package in Debian 11 (bullseye) and Debian 12 (bookworm)
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
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 locallyCheck whether your project pulls in CVE-2022-47184 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-47184 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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