CVE-2021-44716
CVE-2021-44716 is a resource exhaustion in Golang Go (CVSS 7.5, High).
No known exploitation. EPSS puts it in the 91st percentile. Fixed versions are out.
No public exploit knownFix2 products2 fixed builds listed below
e.g. OID 1.3.6.1.4.1.25623.1.0.127537
What to do
Find your product and version, then upgrade to the build on the right.
- Golang.org/x/net/http2Affected: < 0.0.0-20211209124913-491a49abca63Upgrade to: 0.0.0-20211209124913-491a49abca63Stated by: GitHub advisory
- Golang GoAffected: < 1.16.12Upgrade to: 1.16.12Stated by: NVD
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
net/http in Go before 1.16.12 and 1.17.x before 1.17.5 allows uncontrolled memory consumption in the header canonicalization cache via HTTP/2 requests.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
4.3% chance of exploitation activity in the next 30 days, which ranks it in the 91st percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
6 events over 1636 days, from the signal feeds we watch.
- OpenVAS check added
- Patch availablerecord updated
- Publishedweakness classified, att&ck mapped
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Scored 7.5 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity NoneNo integrity impact
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
- groups.google.com/g/golang-announce/c/hcmEScgc00k
- security.netapp.com/advisory/ntap-20220121-0002/
- lists.debian.org/debian-lts-announce/2022/01/msg00016.html
And 19 more references. See all after sign-in
Questions about CVE-2021-44716
- Is CVE-2021-44716 being exploited?
- No exploitation is confirmed and no public exploit is known. EPSS puts the chance of exploitation in the next 30 days at 4.3%.
- Which versions are affected by CVE-2021-44716?
- Go: < 1.16.12. Golang.org/x/net/http2: < 0.0.0-20211209124913-491a49abca63.
- How do I fix or mitigate CVE-2021-44716?
- Upgrade to a fixed build for your product branch: 0.0.0-20211209124913-491a49abca63, 1.16.12. The advisory is on security.gentoo.org.
Last updated
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Go, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI