dbcve.org
Traffic ServerApplication · Apache

CVE-2019-9515

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 settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, 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 settings flood DoS attack where an attacker sends a stream of SETTINGS frames. Since RFC 7540 requires peers to acknowledge each SETTINGS frame individually, an empty SETTINGS frame functions like a ping. The vulnerability allows attackers to exhaust victim CPU or memory by sending many SETTINGS frames faster than they can be processed.

MitigationUpdate affected HTTP/2 implementations to enforce rate limits or reject excessive SETTINGS frames, and configure appropriate resource limits and timeouts for SETTINGS frame handling.

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:= 29= 30
Jboss Core ServicesApplication
Affected:= 1.0
Jboss Enterprise Application PlatformApplication
Affected:= 7.2.0= 7.3.0
Openshift Container PlatformApplication
Affected:= 4.1
Openshift Service MeshApplication
Affected:= 1.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 HTTP/2-enabled services
    Review your server configuration for any service exposing HTTP/2 endpoints (look for 'h2' or 'HTTP/2' in SSL/TLS configurations, proxy configs, or application server settings). Check listening services with: netstat -tlnp | grep -E ':(443|80|8080)\b' or ss -tlnp
    Affected if HTTP/2 is enabled and exposed on any listening service
  2. Determine Apache Traffic Server version
    If Apache Traffic Server is in use, run: traffic_server -version or ats-version. On systems with package managers: dpkg -l trafficserver or rpm -qa trafficserver
    Affected if Installed version falls within 6.0.0-6.2.3, 7.0.0-7.1.6, or 8.0.0-8.0.3
  3. Check base OS HTTP/2 libraries
    For Ubuntu/Debian: dpkg -l | grep -E 'libnghttp2|apache2|nginx'. For Fedora: rpm -qa | grep -E 'nghttp2|httpd|nginx'. Identify the HTTP/2 stack version in use by the OS packages
    Affected if Running Ubuntu 16.04, 18.04, 19.04; Debian 9.0 or 10.0; or Fedora 29 or 30 with HTTP/2-enabled services
  4. Verify Red Hat product versions
    For JBoss Core Services: rpm -qa jboss-core-services. For JBoss EAP: grep -r 'jboss-eap' /opt or check /opt/jboss-*/bin/standalone.sh --version. For OpenShift: oc get clusterversion version
    Affected if JBoss Core Services 1.0, JBoss EAP 7.2.0 or 7.3.0, OpenShift Container Platform 4.1, or OpenShift Service Mesh 1.0 is deployed with HTTP/2 exposed

Your environment is affected if any HTTP/2-enabled service is running on a product version matching the affected ranges listed above, since the vulnerability exists in the HTTP/2 implementation itself when processing SETTINGS frames.

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 to enforce rate limits or reject excessive SETTINGS frames, and configure appropriate resource limits and timeouts for SETTINGS frame handling.

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-9515 — 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-9515 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