Skip to content

golang.org/x/net/http2/h2c vulnerable to request smuggling attack

High severity GitHub Reviewed Published Jan 14, 2023 to the GitHub Advisory Database • Updated May 20, 2024

Package

gomod golang.org/x/net (Go)

Affected versions

>= 0.0.0-20220524220425-1d687d428aca, < 0.1.1-0.20221104162952-702349b0e862

Patched versions

0.1.1-0.20221104162952-702349b0e862

Description

A request smuggling attack is possible when using MaxBytesHandler. When using MaxBytesHandler, the body of an HTTP request is not fully consumed. When the server attempts to read HTTP2 frames from the connection, it will instead be reading the body of the HTTP request, which could be attacker-manipulated to represent arbitrary HTTP2 requests.

Specific Go Packages Affected

golang.org/x/net/http2/h2c

References

Published by the National Vulnerability Database Jan 13, 2023
Published to the GitHub Advisory Database Jan 14, 2023
Reviewed Jan 20, 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

0.173%
(56th percentile)

Weaknesses

CVE ID

CVE-2022-41721

GHSA ID

GHSA-fxg5-wq6x-vr4w

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.