Resource exhaustion in Golang Go
CVE-2022-2879
- CVSS v3
- 7.5 High
- Public exploits
- None known
- EPSS
- 0.020 · 81.2th percentile
- Published
- 2022-10-14
Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - Privileges Required
- None
PR:N - User Interaction
- None
UI:N - Scope
- Unchanged
S:U - Confidentiality
- None
C:N - Integrity
- None
I:N - Availability
- High
A:H
EPSS exploit prediction
EPSS 0.020, 81.2th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Golang Go
- Go Standard Library Archive/tar — versions 0, 1.19.0-0
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 10 other repositories (8-cm/kube-dump, agadecki/malware-cryptominer-container, ARPSyndicate/cvemon, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- go.dev/issue/54853 (Third Party Advisory, Issue Tracking)
- go.dev/cl/439355 (Patch)
- groups.google.com/g/golang-announce/c/xtuG5faxtaU (Mailing List, Release Notes)
- pkg.go.dev/vuln/GO-2022-1037 (Vendor Advisory)
- security.gentoo.org/glsa/202311-09