dbcve.org
Traffic ServerApplication · Apache

CVE-2019-9514

HIGH · 7.5 CVSS v3.1 Published 2019-08-13
Fix available
A fix is available. Upgrade to after 8.0.3 or later.
See remediation →
84/100
Remediation priority · High
High EPSS 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
Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service. The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both.

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

HTTP/2 implementations are vulnerable to a reset flood denial-of-service attack where attackers open multiple streams and send invalid requests to elicit RST_STREAM frames from the peer. The vulnerability stems from how peers queue these RST_STREAM frames, potentially consuming excess memory, CPU, or both.

MitigationImplement rate limiting and proper queue management for RST_STREAM frames to prevent memory and CPU exhaustion from excessive reset frames.

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.6>= 8.0.0, <= 8.0.3
Debian LinuxOperating system
Affected:= 10.0= 9.0
Ubuntu LinuxOperating system
Affected:= 16.04= 18.04= 19.04
FedoraOperating system
Affected:= 29= 30
Developer ToolsApplication
Affected:= 1.0
Jboss Core ServicesApplication
Affected:= 1.0
Jboss Enterprise Application PlatformApplication
Affected:= 7.2.0= 7.3.0
Openshift Container PlatformApplication
Affected:= 3.9= 3.10= 3.11= 4.1= 4.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Check if Apache Traffic Server is installed
    Run command: traffic_server -v or rpm -qa | grep -i traffic-server or dpkg -l | grep -i traffic-server
    Affected if Apache Traffic Server is present on the system
  2. Verify the installed Apache Traffic Server version
    Run: traffic_server -v and compare the version number against the affected ranges: 6.0.0-6.2.3, 7.0.0-7.1.6, or 8.0.0-8.0.3
    Affected if The installed version falls within any of the affected ranges (6.0.0-6.2.3, 7.0.0-7.1.6, or 8.0.0-8.0.3)
  3. Confirm HTTP/2 protocol is enabled
    Check the records.config file for proxy.config.http2.enabled setting, or run: traffic_ctl config get proxy.config.http2.enabled
    Affected if HTTP/2 is enabled (value set to 1) - the vulnerability only applies when HTTP/2 connections are accepted

You are affected if Apache Traffic Server is installed with a version in the 6.0.0-6.2.3, 7.0.0-7.1.6, or 8.0.0-8.0.3 range AND HTTP/2 is enabled in the configuration.

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.

From vendor data
Upgrade available Upgrade to a release after 8.0.3
Interim mitigation

Implement rate limiting and proper queue management for RST_STREAM frames to prevent memory and CPU exhaustion from excessive reset frames.

Fix this in Traffic Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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