dbcve.org
Traffic ServerApplication · Apache

CVE-2019-9513

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 resource loops, potentially leading to a denial of service. The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consume excess CPU.

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

CVE-2019-9513 is a denial-of-service vulnerability in HTTP/2 implementations where attackers exploit the stream priority mechanism by rapidly creating multiple request streams and continually shuffling their priorities. This causes excessive computational overhead as the server repeatedly rebalances the priority tree, leading to CPU exhaustion.

MitigationUpdate affected HTTP/2 implementations (web servers, proxies, load balancers) to versions that address this vulnerability, or temporarily disable HTTP/2 if patches are unavailable.

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
Ubuntu LinuxOperating system
Affected:= 16.04= 18.04= 19.04
Debian LinuxOperating system
Affected:= 9.0= 10.0
FedoraOperating system
Affected:= 30= 29
Jboss Core ServicesApplication
Affected:= 1.0
Jboss Enterprise Application PlatformApplication
Affected:= 7.2.0= 7.3.0
Openshift Service MeshApplication
Affected:= 1.0
QuayApplication
Affected:= 3.0.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
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. Identify installed Apache Traffic Server version
    Run 'trafficserver -v' or check package manager (dpkg -r rpm -q) for apache-traffic-server
    Affected if Version is >= 6.0.0 and <= 6.2.3, OR >= 7.0.0 and <= 7.1.6, OR >= 8.0.0 and <= 8.0.3
  2. Check if HTTP/2 is enabled in Apache Traffic Server
    Inspect configuration file records.config for 'proxy.config.http2.enabled' set to 1, or check any TLS configuration enabling ALPN h2 protocol
    Affected if HTTP/2 is enabled (value set to 1) and version matches affected range from step 1
  3. Identify HTTP/2 server implementations on Linux systems
    Check installed HTTP/2-capable servers: 'dpkg -l' or 'rpm -qa' for nginx, apache2, httpd, or other HTTP/2 implementations
    Affected if Vulnerable HTTP/2 server packages are installed on Ubuntu 16.04, 18.04, 19.04; Debian 9.0, 10.0; or Fedora 29, 30
  4. Check Red Hat product versions
    For JBoss Core Services: 'rpm -q jboss-core-services'; for JBoss EAP: check 'rpm -q jboss-eap' or inspect /opt/jboss-eap-*/bin/standalone.sh version; for Quay: 'docker images quay.io/quay/quay' or 'rpm -q quay'
    Affected if JBoss Core Services = 1.0, JBoss EAP = 7.2.0 or 7.3.0, Quay = 3.0.0, or OpenShift Service Mesh = 1.0 is installed with HTTP/2 exposed

Your environment is affected if any of the identified products match the specific version ranges AND HTTP/2 protocol is enabled and exposed to untrusted network traffic.

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

Update affected HTTP/2 implementations (web servers, proxies, load balancers) to versions that address this vulnerability, or temporarily disable HTTP/2 if patches are unavailable.

Fix this in Traffic Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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