Loading HuntDB...

CVE-2023-44487

HIGH
Published 2023-10-10T00:00:00.000Z
Actions:

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2023-44487. We'll provide specific mitigation strategies based on your environment and risk profile.

CVSS Score

V3.1
7.5
/10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Base Score Metrics
Exploitability: N/A Impact: N/A

EPSS Score

v2025.03.14
0.945
probability
of exploitation in the wild

There is a 94.5% chance that this vulnerability will be exploited in the wild within the next 30 days.

Updated: 2025-06-25
Exploit Probability
Percentile: 1.000
Higher than 100.0% of all CVEs

Attack Vector Metrics

Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED

Impact Metrics

Confidentiality
NONE
Integrity
NONE
Availability
HIGH

Description

The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

Affected Versions:

Known Exploited Vulnerability

This vulnerability is actively being exploited in the wild

View KEV Details

Remediation Status

Overdue

Due Date

October 31, 2023

Added to KEV

October 10, 2023

Required Action

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Affected Product

Vendor/Project: IETF
Product: HTTP/2

Ransomware Risk

Known Ransomware Use
KEV Catalog Version: 2025.01.24 Released: January 24, 2025

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

✓ GitHub Reviewed MODERATE

HTTP/2 Stream Cancellation Attack

GHSA-qppj-fm5r-hxr3

Advisory Details

## HTTP/2 Rapid reset attack The HTTP/2 protocol allows clients to indicate to the server that a previous stream should be canceled by sending a RST_STREAM frame. The protocol does not require the client and server to coordinate the cancellation in any way, the client may do it unilaterally. The client may also assume that the cancellation will take effect immediately when the server receives the RST_STREAM frame, before any other data from that TCP connection is processed. Abuse of this feature is called a Rapid Reset attack because it relies on the ability for an endpoint to send a RST_STREAM frame immediately after sending a request frame, which makes the other endpoint start working and then rapidly resets the request. The request is canceled, but leaves the HTTP/2 connection open. The HTTP/2 Rapid Reset attack built on this capability is simple: The client opens a large number of streams at once as in the standard HTTP/2 attack, but rather than waiting for a response to each request stream from the server or proxy, the client cancels each request immediately. The ability to reset streams immediately allows each connection to have an indefinite number of requests in flight. By explicitly canceling the requests, the attacker never exceeds the limit on the number of concurrent open streams. The number of in-flight requests is no longer dependent on the round-trip time (RTT), but only on the available network bandwidth. In a typical HTTP/2 server implementation, the server will still have to do significant amounts of work for canceled requests, such as allocating new stream data structures, parsing the query and doing header decompression, and mapping the URL to a resource. For reverse proxy implementations, the request may be proxied to the backend server before the RST_STREAM frame is processed. The client on the other hand paid almost no costs for sending the requests. This creates an exploitable cost asymmetry between the server and the client. Multiple software artifacts implementing HTTP/2 are affected. This advisory was originally ingested from the `swift-nio-http2` repo advisory and their original conent follows. ## swift-nio-http2 specific advisory swift-nio-http2 is vulnerable to a denial-of-service vulnerability in which a malicious client can create and then reset a large number of HTTP/2 streams in a short period of time. This causes swift-nio-http2 to commit to a large amount of expensive work which it then throws away, including creating entirely new `Channel`s to serve the traffic. This can easily overwhelm an `EventLoop` and prevent it from making forward progress. swift-nio-http2 1.28 contains a remediation for this issue that applies reset counter using a sliding window. This constrains the number of stream resets that may occur in a given window of time. Clients violating this limit will have their connections torn down. This allows clients to continue to cancel streams for legitimate reasons, while constraining malicious actors.

Affected Packages

SwiftURL github.com/apple/swift-nio-http2
ECOSYSTEM: ≥0 <1.28.0
Go golang.org/x/net
ECOSYSTEM: ≥0 <0.17.0
Go google.golang.org/grpc
ECOSYSTEM: ≥1.58.0 <1.58.3
Go google.golang.org/grpc
ECOSYSTEM: ≥1.57.0 <1.57.1
Go google.golang.org/grpc
ECOSYSTEM: ≥0 <1.56.3
Maven org.apache.tomcat:tomcat-coyote
ECOSYSTEM: ≥11.0.0-M1 <11.0.0-M12
Maven org.apache.tomcat:tomcat-coyote
ECOSYSTEM: ≥10.0.0 <10.1.14
Maven org.apache.tomcat:tomcat-coyote
ECOSYSTEM: ≥9.0.0 <9.0.81
Maven org.apache.tomcat:tomcat-coyote
ECOSYSTEM: ≥8.5.0 <8.5.94
Maven org.apache.tomcat.embed:tomcat-embed-core
ECOSYSTEM: ≥11.0.0-M1 <11.0.0-M12
Maven org.apache.tomcat.embed:tomcat-embed-core
ECOSYSTEM: ≥10.0.0 <10.1.14
Maven org.apache.tomcat.embed:tomcat-embed-core
ECOSYSTEM: ≥9.0.0 <9.0.81
Maven org.apache.tomcat.embed:tomcat-embed-core
ECOSYSTEM: ≥8.5.0 <8.5.94
Maven org.eclipse.jetty.http2:http2-common
ECOSYSTEM: ≥9.3.0 <9.4.53
Maven org.eclipse.jetty.http2:http2-common
ECOSYSTEM: ≥10.0.0 <10.0.17
Maven org.eclipse.jetty.http2:http2-common
ECOSYSTEM: ≥11.0.0 <11.0.17
Maven org.eclipse.jetty.http2:http2-server
ECOSYSTEM: ≥9.3.0 <9.4.53
Maven org.eclipse.jetty.http2:http2-server
ECOSYSTEM: ≥10.0.0 <10.0.17
Maven org.eclipse.jetty.http2:http2-server
ECOSYSTEM: ≥11.0.0 <11.0.17
Maven org.eclipse.jetty.http2:jetty-http2-common
ECOSYSTEM: ≥12.0.0 <12.0.2
Maven org.eclipse.jetty.http2:jetty-http2-server
ECOSYSTEM: ≥12.0.0 <12.0.2
Maven com.typesafe.akka:akka-http-core
ECOSYSTEM: ≥0 <10.5.3
Maven com.typesafe.akka:akka-http-core_2.13
ECOSYSTEM: ≥0 <10.5.3
Maven com.typesafe.akka:akka-http-core_2.12
ECOSYSTEM: ≥0 <10.5.3
Maven com.typesafe.akka:akka-http-core_2.11
ECOSYSTEM: ≥0 ≤10.1.15

CVSS Scoring

CVSS Score

5.0

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

References

Advisory provided by GitHub Security Advisory Database. Published: October 10, 2023, Modified: June 9, 2025

References

Published: 2023-10-10T00:00:00.000Z
Last Modified: 2025-03-07T18:15:13.812Z
Copied to clipboard!