LiveActive security incident?Get immediate response
CVE Record

CVE-2022-30631: Stack exhaustion when reading certain archives in compress/gzip

Uncontrolled recursion in Reader.Read in compress/gzip before Go 1.17.12 and Go 1.18.4 allows an attacker to cause a panic due to stack exhaustion via an archive containing a large number of concatenated 0-length compressed files.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Go program that reads attacker-supplied gzip data could be crashed by a specially structured archive. The impact is service availability, not data theft or code execution based on the provided sources. Systems built with Go before 1.17.12 or 1.18.4 are the concern.

Executive priority

Treat as a high-priority availability risk for internet-facing or automated ingestion systems. It is not described as data compromise, but a crashable service can still create operational disruption.

Technical view

compress/gzip Reader.Read used uncontrolled recursion when processing concatenated zero-length compressed files. A gzip stream with many such members could exhaust the stack and panic. The flaw is tracked as CWE-674 and GO-2022-0524, fixed in Go 1.17.12 and 1.18.4.

Likely exposure

Exposure is most likely in Go services, APIs, file processors, or ingestion pipelines that accept untrusted gzip archives or compressed streams and were built with affected Go versions.

Exploitation context

The CVSS vector indicates remote, unauthenticated, low-complexity denial of service. The bundle does not show CISA KEV listing or other evidence of active exploitation, so exploitation should not be claimed as observed.

Researcher notes

Focus validation on reachability: vulnerable Go version plus attacker-controlled gzip input reaching compress/gzip.Reader.Read. The public sources identify stack exhaustion through recursive handling of many concatenated zero-length gzip members, with fixes landed in Go security releases.

Mitigation direction

  • Upgrade Go toolchains to 1.17.12, 1.18.4, or later supported releases.
  • Rebuild and redeploy affected Go binaries after upgrading the toolchain.
  • Prioritize services that parse gzip data from users, partners, or the internet.
  • Check Go vendor guidance and GO-2022-0524 records for affected-version details.
  • Temporarily reduce exposure of untrusted gzip ingestion paths where patching is delayed.

Validation and detection

  • Inventory deployed Go binaries and their build toolchain versions.
  • Identify code paths using compress/gzip on untrusted archives or streams.
  • Confirm rebuilt services use Go 1.17.12, 1.18.4, or later.
  • Use vulnerability management results mapped to GO-2022-0524 where available.
  • Run regression tests for gzip handling after rebuilding.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-674: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-30631 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-30631Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Go standard librarycompress/gzipcompress/gzip, 0, 1.18.0-0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-674 · source CWE mapping

Uncontrolled Recursion

Uncontrolled Recursion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.