Resource exhaustion in Golang Go
CVE-2022-2879
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.
EPSS: 0.016 (73.3th percentile) — read the EPSS interpretation.
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.
Affected products
- Golang Go
- Go Standard Library Archive/tar — versions 0, 1.19.0-0
Weakness classification (CWE)
Public proof-of-concept exploits
References
- security@golang.org (Third Party Advisory, Issue Tracking)
- security@golang.org (Patch)
- security@golang.org (Mailing List, Release Notes)
- security@golang.org (Vendor Advisory)
- security@golang.org
Frequently asked questions
- What is CVE-2022-2879?
- CVE-2022-2879 is a high-severity vulnerability in Golang Go, classified under Allocation of Resources Without Limits or Throttling. CVSS score: 7.5/10. Published 2022-10-14.
- How severe is CVE-2022-2879?
- High severity. CVSS v3 base score is 7.5 out of 10.
- Is CVE-2022-2879 known to be exploited?
- 10 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.