LiveActive security incident?Get immediate response
CVE Record

CVE-2022-30635: Stack exhaustion when decoding certain messages in encoding/gob

Uncontrolled recursion in Decoder.Decode in encoding/gob before Go 1.17.12 and Go 1.18.4 allows an attacker to cause a panic due to stack exhaustion via a message which contains deeply nested structures.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A maliciously crafted gob message can make affected Go programs crash by exhausting the call stack during decoding. The impact is denial of service, not data theft or data modification. Business urgency depends on whether internet-facing or tenant-facing services decode untrusted gob data.

Executive priority

Treat this as a high-priority availability risk for Go services that parse untrusted gob data. Patch during normal urgent maintenance, faster for internet-facing or multi-tenant systems. It is not evidenced as actively exploited in the provided sources.

Technical view

CVE-2022-30635 is uncontrolled recursion in Go's encoding/gob Decoder.Decode before Go 1.17.12 and Go 1.18.4. Deeply nested structures can trigger stack exhaustion and panic. CVSS 7.5 reflects network-reachable, unauthenticated availability impact with no confidentiality or integrity impact.

Likely exposure

Exposure is likely in Go services, APIs, or internal components that decode attacker-controlled gob messages using affected Go standard library versions. Systems that do not use encoding/gob, or only decode trusted local data, have lower practical exposure.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The described attack condition is a crafted deeply nested gob message sent to software that decodes untrusted gob input, causing process panic and service disruption.

Researcher notes

The root issue is CWE-674 uncontrolled recursion during gob decoding. The public record supports denial-of-service through stack exhaustion only. Evidence is strongest for affected Go standard library versions and the patched release boundary; exploit prevalence and product-specific exposure are not established here.

Mitigation direction

  • Upgrade Go to 1.17.12, 1.18.4, or a later supported release.
  • Rebuild and redeploy affected Go binaries after upgrading the toolchain.
  • Prioritize services that decode gob data from network or tenant-controlled sources.
  • Avoid accepting untrusted gob input where safer formats or trust boundaries are available.
  • Check official Go vulnerability guidance for any environment-specific remediation notes.

Validation and detection

  • Inventory Go binaries and build toolchains for versions before 1.17.12 or 1.18.4.
  • Search code for encoding/gob Decoder.Decode usage and map input trust boundaries.
  • Confirm exposed services do not decode unauthenticated or tenant-controlled gob data.
  • Verify rebuilt binaries use patched Go versions in production.
  • Review monitoring for unexplained panics or availability drops in gob-decoding services.
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-30635 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-30635Attack 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 libraryencoding/gobencoding/gob, 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.