CVE-2019-9512
Some HTTP/2 implementations are vulnerable to ping floods, potentially leading to a denial of service
CVE-2019-9512 is a resource exhaustion in Go golang.org/x/net (CVSS 7.5, High).
Exploitation likely. EPSS gives it a 84% chance of exploitation in the next 30 days. Fixed in 0.0.0-20190813141303-74dc4d7220e7.
No public exploit knownFix0.0.0-20190813141303-74dc4d7220e7Upgrade to this build
e.g. OID 1.3.6.1.4.1.25623.1.0.142750
What to do
Find your product and version, then upgrade to the build on the right.
- Golang.org/x/netAffected: < 0.0.0-20190813141303-74dc4d7220e7Upgrade to: 0.0.0-20190813141303-74dc4d7220e7Stated by: GitHub advisory
- Apple SwiftnioAffected: ≥ 1.0.0, ≤ 1.4.0Upgrade to: after 1.4.0Stated by: NVD
- Apache Traffic ServerAffected: ≥ 6.0.0, ≤ 6.2.3Upgrade to: after 6.2.3Stated by: NVD
- Nodejs Node.jsAffected: ≥ 8.0.0, ≤ 8.8.1Upgrade to: after 8.8.1Stated by: NVD
- Open-source community Debian GNU/LinuxAffected: 9Upgrade to: not statedStated by: BDU
Versions as the sources state them. 6 more products have version data. Full version matrix after sign-in
What it is
From the CVE record
golang.org/x/net/http vulnerable to ping floods
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
84% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
6 events over 2508 days, from the signal feeds we watch.
- OpenVAS check added
- Patch availablerecord updated
- Publishedweakness classified, att&ck mapped
Affected products
And 17 more affected products. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Scored 7.5 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity NoneNo integrity impact
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
- nvd.nist.gov/vuln/detail/CVE-2019-9512
- github.com/Netflix/security-bulletins/blob/master/advisories/third-party/2019-002.md
- go.dev/cl/190137
And 94 more references. See all after sign-in
Questions about CVE-2019-9512
- Is CVE-2019-9512 being exploited?
- No exploitation is confirmed and no public exploit is known. EPSS puts the chance of exploitation in the next 30 days at 84%.
- Which versions are affected by CVE-2019-9512?
- Golang.org/x/net: < 0.0.0-20190813141303-74dc4d7220e7. Swiftnio: ≥ 1.0.0, ≤ 1.4.0. Traffic Server: ≥ 6.0.0, ≤ 6.2.3. 8 more products are listed in the record.
- How do I fix or mitigate CVE-2019-9512?
- Upgrade to 0.0.0-20190813141303-74dc4d7220e7 or later. The advisory is on github.com.
Last updated
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Golang.org/x/net, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI