dbcve.org
Traffic ServerApplication · Apache

CVE-2019-9512

HIGH · 7.5 CVSS v3.1 Published 2019-08-13
Fix available
A fix is available. Upgrade to 8.16.1 / 10.16.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 ping floods, potentially leading to a denial of service. The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. 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 ping floods where attackers send continual PING frames faster than the server can process them. The peer builds an internal queue of responses that, depending on queue efficiency, consumes excess CPU, memory, or both, leading to denial of service.

MitigationImplement rate limiting on incoming PING frames at the application or network level, and configure queue depth limits and timeouts to bound resource consumption per HTTP/2 connection.

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
Node.jsApplication
Affected:>= 8.0.0, <= 8.8.1>= 8.9.0, < 8.16.1>= 10.0.0, <= 10.12.0>= 10.13.0, < 10.16.3>= 12.0.0, < 12.8.1
SwiftnioApplication
Affected:>= 1.0.0, <= 1.4.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 'traffic_server -v' or check package manager (dpkg -l | grep traffic-server, rpm -q 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. Verify Apache Traffic Server HTTP/2 enablement
    Check configuration file (records.config) for 'proxy.config.http2.enabled' setting or inspect active configuration via traffic_ctl config get proxy.config.http2.enabled
    Affected if HTTP/2 is enabled (value is 1 or true) on an affected version
  3. Identify installed Node.js version
    Run 'node --version' to get the major.minor.patch version
    Affected if Version falls within 8.0.0-8.8.1, 8.9.0-8.16.0, 10.0.0-10.12.0, 10.13.0-10.16.2, or 12.0.0-12.8.0
  4. Verify Node.js HTTP/2 usage
    Inspect application code for http2 module usage (const http2 = require('http2') or import http2 from 'http2'), or check if the Node.js process handles HTTP/2 connections
    Affected if Application uses the http2 module or serves HTTP/2 traffic on an affected Node.js version
  5. Identify installed SwiftNIO version
    Check Package.swift dependencies or run 'swift package show-dependencies' for swift-nio, or check installed NIO version via package manager
    Affected if SwiftNIO version is >= 1.0.0 and <= 1.4.0
  6. Verify SwiftNIO HTTP/2 enablement
    Inspect application code for HTTP2StreamChannel or NIOHTTP2Handler usage in the server bootstrap configuration
    Affected if HTTP/2 handler is configured in the channel pipeline on an affected SwiftNIO version

You are affected if you run any of the listed product versions AND have HTTP/2 enabled or actively handle HTTP/2 connections.

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 8.16.1 / 10.16.3 / 12.8.1 or later
Fixed in 8.16.110.16.312.8.1
Interim mitigation

Implement rate limiting on incoming PING frames at the application or network level, and configure queue depth limits and timeouts to bound resource consumption per HTTP/2 connection.

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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