webtransport-go: Memory Exhaustion Attack due to Buffering of Unknown Capsules
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| quic-go | webtransport-go | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Quic-go | Webtransport-go |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-g35j-m5xg-vh3q | webtransport-go: Memory Exhaustion Attack due to Buffering of Unknown Capsules |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.524% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Quic-go
Quic-go webtransport-go |
|
| Vendors & Products |
Quic-go
Quic-go webtransport-go |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | webtransport-go is an implementation of the WebTransport protocol. Prior to 0.11.1, Session.parseNextCapsule() in session.go skips an unknown WebTransport capsule on the HTTP/3 request stream by calling io.ReadAll on the capsule reader, retaining the complete declared capsule body in memory. A malicious peer can send a large unknown capsule and cause a client or server to allocate memory for the full payload; QUIC flow control does not bound the total retained allocation because reading advances the flow-control window while the received bytes remain in memory. The resulting memory and resource exhaustion can disrupt or crash the affected process. This issue is fixed in version 0.11.1. | |
| Title | webtransport-go: Memory Exhaustion Attack due to Buffering of Unknown Capsules | |
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
cvssV3_1
|