GO-2022-0288 BIT-golang-2021-44716 CVE-2021-44716 GHSA-vc3p-29h2-gpcp
Unbounded memory growth in net/http and golang.org/x/net/http2
High
Go
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 4.25%
- Chance of exploitation in the next 30 days. Higher than 91.06% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
- Available
- 3 packages have a fixed version
Description
An attacker can cause unbounded memory growth in servers accepting HTTP/2 requests.
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| golang.org/x/net | < 0.0.0-20211209124913-491a49abca63 |
0.0.0-20211209124913-491a49abca63 |
| golang.org/x/net/http2 | < 0.0.0-20211209124913-491a49abca63 |
0.0.0-20211209124913-491a49abca63 |
| stdlib | < 1.16.12>= 1.17.0-0, < 1.17.5 |
1.16.121.17.5 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
golang.org/x/net Go → 0.0.0-20211209124913-491a49abca63
- go
go get golang.org/x/net@v0.0.0-20211209124913-491a49abca63 && go mod tidy
golang.org/x/net/http2 Go → 0.0.0-20211209124913-491a49abca63
- go
go get golang.org/x/net/http2@v0.0.0-20211209124913-491a49abca63 && go mod tidy
stdlib Go → 1.17.5
- go
go get stdlib@v1.17.5 && go mod tidy
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Weakness
CWE-400: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How to prevent it
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
References
Advisories
Other links
- go.dev/cl/369794
- go.dev/issue/50058
- groups.google.com/g/golang-announce/c/hcmEScgc00k
- lists.debian.org/debian-lts-announce/2022/01/msg00016.html
- lists.debian.org/debian-lts-announce/2022/01/msg00017.html
- pkg.go.dev/vuln/GO-2022-0288
- security.gentoo.org/glsa/202208-02
- security.netapp.com/advisory/ntap-20220121-0002
- cert-portal.siemens.com/productcert/pdf/ssa-744259.pdf
- lists.debian.org/debian-lts-announce/2023/04/msg00021.html
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-4374-p667-p6c8 HTTP/2 rapid reset can cause excessive work in net/http | High Known exploited | Also affects golang.org/x/net |
| GHSA-qppj-fm5r-hxr3 HTTP/2 Stream Cancellation Attack | Medium Known exploited | Also affects golang.org/x/net |
| CVE-2020-0601 Certificate validation bypass on Windows in crypto/x509 | High Known exploited | Also affects stdlib |
| GO-2026-6866 Check all ancestor namespace transitions when rendering raw text in html in golang.org/x/net | Not rated yet | Also affects golang.org/x/net |
| GO-2026-6860 Avoid quadratic complexity when coalescing text nodes in html in golang.org/x/net | Not rated yet | Also affects golang.org/x/net |
| RUSTSEC-2026-0382 Distrust compromised intermediate certificates in crypto/x509 | Medium | Also affects stdlib |
| GO-2026-6613 HTTP/1 server connection desynchronization after 2xx CONNECT response in net/http | High | Also affects stdlib |
| GO-2026-6609 Lack of limit on size of parsed Range headers in net/http | High | Also affects stdlib |
Credits: murakmii
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor