dbcve.org
Traffic ServerApplication · Apache

CVE-2019-17559

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-23
Fix available
A fix is available. Upgrade to after 8.0.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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
There 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 scheme parsing. 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 · high confidence

Apache Traffic Server contains an HTTP smuggling vulnerability related to scheme parsing. Attackers can exploit inconsistencies in how the proxy parses HTTP request schemes to bypass security controls, inject malicious requests, or access restricted resources. This affects the TS-4501 security fix area in the proxy processing pipeline.

MitigationUpgrade Apache Traffic Server to version 7.1.9, 8.0.6, or later to patch the vulnerability. For systems that cannot be immediately upgraded, implement additional request validation at upstream proxies and monitor for anomalous traffic patterns indicative of smuggling attempts.

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:>= 6.0.0, <= 6.2.3>= 7.0.0, <= 7.1.8>= 8.0.0, <= 8.0.5
Debian LinuxOperating system
Affected:= 10.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Apache Traffic Server is installed
    Run `traffic_server -V` or check via package manager (e.g., `dpkg -l | grep trafficserver` on Debian, `rpm -qa | grep trafficserver` on RHEL)
    Affected if Command returns a version number indicating Apache Traffic Server is present
  2. Determine installed version
    Extract the exact version number from the output of `traffic_server -V` or package query command
    Affected if The returned version falls within any of these ranges: 6.0.0 to 6.2.3, 7.0.0 to 7.1.8, or 8.0.0 to 8.0.5 (inclusive)
  3. Confirm proxy processing is enabled
    Inspect the Traffic Server configuration file (records.config) and verify `proxy.config.http.enable` is set to `1` or check that the proxy port is configured in records.config under `proxy.config.http.server_ports`
    Affected if Proxy processing is enabled (value is 1 or a proxy port is configured)
  4. Check for exposed proxy interface
    Review records.config for `proxy.config.http.insert_squid_x_forwarded_for` or similar proxy-related settings, and verify the proxy listener is bound to an accessible network interface (not localhost-only)
    Affected if The proxy is listening on a non-internal interface and accessible to potential attackers

You are affected if Apache Traffic Server is running with proxy enabled AND the installed version falls within 6.0.0-6.2.3, 7.0.0-7.1.8, or 8.0.0-8.0.5.

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 a release after 8.0.5
Interim mitigation

Upgrade Apache Traffic Server to version 7.1.9, 8.0.6, or later to patch the vulnerability. For systems that cannot be immediately upgraded, implement additional request validation at upstream proxies and monitor for anomalous traffic patterns indicative of smuggling attempts.

Recommended fix High confidence

Apache Traffic Server 7.1.9+ or 8.0.6+ (or latest 7.x/8.x stable release)

  1. 1. Identify the currently installed Apache Traffic Server version using: `traffic_server -V` or `ats -V`
  2. 2. For Debian systems, check the installed package version: `dpkg -l | grep trafficserver`
  3. 3. For Traffic Server 7.x (7.0.0 to 7.1.8): Upgrade to version 7.1.9 or later (e.g., 7.2.0, 7.3.0)
  4. 4. For Traffic Server 8.x (8.0.0 to 8.0.5): Upgrade to version 8.0.6 or later (e.g., 8.1.0, 8.2.0)
  5. 5. For Debian 10.0: Update package repositories and upgrade: `apt update && apt install trafficserver`
  6. 6. If using Apache Traffic Server from source: Download the fixed version from https://traffic.apache.org/downloads/
  7. 7. Rebuild and reinstall the new version following standard build procedures
  8. 8. After upgrade, verify the new version is running: `traffic_server -V`
Caveat Minor/patch upgrades within the same major version typically have no breaking changes; however, review release notes for any configuration or 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
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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