Skip to content

golang.org/x/net/http vulnerable to a reset flood

High severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated May 20, 2024

Package

gomod golang.org/x/net (Go)

Affected versions

< 0.0.0-20190813141303-74dc4d7220e7

Patched versions

0.0.0-20190813141303-74dc4d7220e7

Description

Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service. Servers that accept direct connections from untrusted clients could be remotely made to allocate an unlimited amount of memory, until the program crashes. 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.

Specific Go Packages Affected

golang.org/x/net/http2

References

Published by the National Vulnerability Database Aug 13, 2019
Published to the GitHub Advisory Database May 24, 2022
Reviewed Feb 8, 2023
Last updated May 20, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

81.978%
(98th percentile)

Weaknesses

CVE ID

CVE-2019-9514

GHSA ID

GHSA-39qc-96h7-956f

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.