Traffic ServerApplication · Apache
CVE-2019-17565
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 · uneditedThere is a vulnerability in Apache Traffic Server 6.0.0 to 6.2.3, 7.0.0 to 7.1.8, and 8.0.0 to 8.0.5 with a smuggling attack and chunked encoding. Upgrade to versions 7.1.9 and 8.0.6 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 · moderate confidenceApache Traffic Server versions 6.x through 8.0.5 contain a request smuggling vulnerability that exploits chunked encoding, allowing attackers to bypass security controls and perform smuggling attacks. The flaw enables malicious actors to inject crafted requests through chunked transfer encoding that are processed inconsistently by the server and upstream proxies.
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
>= 6.0.0, <= 6.2.3>= 7.0.0, <= 7.1.8>= 8.0.0, <= 8.0.5
Debian LinuxOperating system
= 10.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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Apache Traffic Server is installedRun 'traffic_server -V' or query the package manager (dpkg -l | grep -i traffic or rpm -qa | grep -i traffic)Affected if Apache Traffic Server is present on the system
-
Verify the installed version against affected rangesCompare the version output from step 1 to the affected ranges: 6.0.0 through 6.2.3, 7.0.0 through 7.1.8, or 8.0.0 through 8.0.5Affected if Version falls within any of these ranges: 6.0.0-6.2.3, 7.0.0-7.1.8, or 8.0.0-8.0.5
-
Confirm chunked transfer encoding is being processedReview the records.config file (typically in /etc/trafficserver/) for proxy.config.http.chunked_encoding_enabled or inspect HTTP traffic logs for Transfer-Encoding: chunked headersAffected if Chunked encoding is enabled and the server accepts chunked request bodies from clients or forwards them to upstream servers
If Apache Traffic Server is installed with a version between 6.0.0 and 6.2.3, 7.0.0 and 7.1.8, or 8.0.0 and 8.0.5, and the server processes chunked transfer-encoded requests, the environment is vulnerable to request smuggling.
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 · scopedUpgrade Apache Traffic Server to version 7.1.9, 8.0.6, or later to remediate the chunked encoding smuggling vulnerability.
Traffic Server 7.1.9 or 8.0.6 (or latest stable release)
- 1. Back up your current Apache Traffic Server configuration and data directories
- 2. Stop the Traffic Server service
- 3. Download the fixed version (7.1.9 or 8.0.6 or later) from the official Apache Traffic Server distribution (https://traffic.apache.org/downloads/)
- 4. Install the new version using your system's package manager or from source
- 5. Restore your configuration files from the backup
- 6. Start the Traffic Server service
- 7. Verify the server is running correctly and monitoring for normal operation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Traffic Server
Scoped from the published advisory
- Consultation4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17565 — 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-2019-17565 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