CVE-2023-44487

SOURCE - github

Summary

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 Channels to serve the traffic. This can easily overwhelm an EventLoop and prevent it from making forward progress.

Impacted images

GitHub

CREATED

10 months ago

UPDATED

1 month ago

SOURCE IDGHSA-qppj-fm5r-hxr3⁠

EXPLOITABILITY SCORE

3.9

EXPLOITS FOUND

COMMON WEAKNESS ENUMERATION (CWE)

CWE-400⁠

CVSS SCORE

5.3medium

Package	Type	OS Name	OS Version	Affected Ranges	Fix Versions
google.golang.org/grpc	golang	-	-	<1.56.3	1.56.3
com.typesafe.akka/akka-http-core	maven	-	-	<10.5.3	10.5.3
com.typesafe.akka/akka-http-core_2.11	maven	-	-	<=10.1.15	Not yet available
com.typesafe.akka/akka-http-core_2.12	maven	-	-	<10.5.3	10.5.3
com.typesafe.akka/akka-http-core_2.13	maven	-	-	<10.5.3	10.5.3
github.com/apple/swift-nio-http2	swifturl	-	-	<1.28.0	1.28.0
golang.org/x/net	golang	-	-	<0.17.0	0.17.0
google.golang.org/grpc	golang	-	-	>=1.57.0,<1.57.1	1.57.1
google.golang.org/grpc	golang	-	-	>=1.58.0,<1.58.3	1.58.3
org.apache.tomcat.embed/tomcat-embed-core	maven	-	-	>=10.0.0,<10.1.14	10.1.14
org.apache.tomcat.embed/tomcat-embed-core	maven	-	-	>=11.0.0-M1,<11.0.0-M12	11.0.0-M12
org.apache.tomcat.embed/tomcat-embed-core	maven	-	-	>=8.5.0,<8.5.94	8.5.94
org.apache.tomcat.embed/tomcat-embed-core	maven	-	-	>=9.0.0,<9.0.81	9.0.81
org.apache.tomcat/tomcat	maven	-	-	>=10.0.0,<10.1.14	10.1.14
org.apache.tomcat/tomcat	maven	-	-	>=11.0.0-M1,<11.0.0-M12	11.0.0-M12
org.apache.tomcat/tomcat	maven	-	-	>=8.5.0,<8.5.94	8.5.94
org.apache.tomcat/tomcat	maven	-	-	>=9.0.0,<9.0.81	9.0.81
org.eclipse.jetty.http2/http2-common	maven	-	-	>=10.0.0,<10.0.17	10.0.17
org.eclipse.jetty.http2/http2-common	maven	-	-	>=11.0.0,<11.0.17	11.0.17
org.eclipse.jetty.http2/http2-common	maven	-	-	>=9.3.0,<9.4.53	9.4.53
org.eclipse.jetty.http2/http2-server	maven	-	-	>=10.0.0,<10.0.17	10.0.17
org.eclipse.jetty.http2/http2-server	maven	-	-	>=11.0.0,<11.0.17	11.0.17
org.eclipse.jetty.http2/http2-server	maven	-	-	>=9.3.0,<9.4.53	9.4.53
org.eclipse.jetty.http2/jetty-http2-common	maven	-	-	>=12.0.0,<12.0.2	12.0.2
org.eclipse.jetty.http2/jetty-http2-server	maven	-	-	>=12.0.0,<12.0.2	12.0.2

CVSS:3 Severity and metrics

The CVSS metrics represent different qualitative aspects of a vulnerability that impact the overall score, as defined by the CVSS Specification⁠.

Attack Vector (AV)

Network

The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone). One example of an Adjacent attack would be an ARP (IPv4) or neighbor discovery (IPv6) flood leading to a denial of service on the local LAN segment (e.g., CVE-2013-6014).

Attack Complexity (AC)

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required (PR)

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.

User Interaction (UI)

None

The vulnerable system can be exploited without interaction from any user.

Scope (S)

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Confidentiality (C)

None

There is no loss of confidentiality.

Integrity (I)

None

There is no loss of trust or accuracy within the impacted component.

Availability (A)

Low

Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Docker

CREATED

10 months ago

UPDATED

10 months ago

SOURCE ID

BSA-2023-44487

EXPLOITABILITY SCORE

EXPLOITS FOUND

COMMON WEAKNESS ENUMERATION (CWE)-

RATING UNAVAILABLE FROM SOURCE

NIST

CREATED

10 months ago

UPDATED

18 hours ago

SOURCE IDCVE-2023-44487⁠

EXPLOITABILITY SCORE

3.9

EXPLOITS FOUND

COMMON WEAKNESS ENUMERATION (CWE)

CWE-400⁠

CVSS SCORE

7.5high

Alpine

CREATED

10 months ago

UPDATED

2 months ago

SOURCE IDCVE-2023-44487⁠

EXPLOITABILITY SCORE

EXPLOITS FOUND

COMMON WEAKNESS ENUMERATION (CWE)-

RATING UNAVAILABLE FROM SOURCE

Debian

CREATED

10 months ago

UPDATED

24 days ago

SOURCE IDCVE-2023-44487⁠

EXPLOITABILITY SCORE

EXPLOITS FOUND

COMMON WEAKNESS ENUMERATION (CWE)-

CVSS SCORE

N/Alow

Ubuntu

CREATED

10 months ago

CREATED

10 months ago

UPDATED

CREATED

10 months ago

CREATED

10 months ago

UPDATED

4 months ago

SOURCE IDCVE-2023-44487⁠

EXPLOITABILITY SCORE

EXPLOITS FOUND

COMMON WEAKNESS ENUMERATION (CWE)-

RATING UNAVAILABLE FROM SOURCE

CISA

CREATED

10 months ago

UPDATED

10 months ago

SOURCE ID

CVE-2023-44487

EXPLOITABILITY SCORE

EXPLOITS FOUND

COMMON WEAKNESS ENUMERATION (CWE)-

RATING UNAVAILABLE FROM SOURCE

vulncheck

CREATED

10 months ago

UPDATED

2 months ago

SOURCE ID

CVE-2023-44487

EXPLOITABILITY SCORE

EXPLOITS FOUND

COMMON WEAKNESS ENUMERATION (CWE)-

RATING UNAVAILABLE FROM SOURCE