LiveActive security incident?Get immediate response
CVE Record

CVE-2022-1962: Stack exhaustion due to deeply nested types in go/parser

Uncontrolled recursion in the Parse functions in go/parser before Go 1.17.12 and Go 1.18.4 allow an attacker to cause a panic due to stack exhaustion via deeply nested types or declarations.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-1962 is a denial-of-service issue in Go's go/parser. If software built with affected Go versions parses specially deep Go type or declaration structures, the process can panic from stack exhaustion. This mainly threatens availability, not data theft or modification.

Executive priority

Prioritize remediation for externally exposed code-analysis, CI, or upload workflows that parse Go source. For trusted internal developer workflows, schedule through normal patch management unless crashes are already observed.

Technical view

The vulnerability is uncontrolled recursion in go/parser Parse functions before Go 1.17.12 and Go 1.18.4. Deeply nested types or declarations can exhaust stack space and trigger a panic. The CVSS vector indicates local attack, low complexity, low privileges, no user interaction, and high availability impact.

Likely exposure

Exposure is most likely in Go-based tools or services that use go/parser to process untrusted Go source. Internal-only parsing of trusted source code has lower practical risk. The source bundle does not identify specific downstream products or internet-wide exposure.

Exploitation context

The bundle does not report active exploitation, and KEV status is false. The described impact is process crash through parser recursion, not code execution. Treat exploitation evidence as incomplete beyond the public vulnerability description and Go references.

Researcher notes

Focus triage on trust boundaries around Go source parsing. The affected component is the Go standard library go/parser, fixed in Go 1.17.12 and 1.18.4. Avoid broad product claims unless a specific application parses attacker-controlled Go code with vulnerable builds.

Mitigation direction

  • Upgrade affected Go environments to Go 1.17.12, Go 1.18.4, or later supported releases.
  • Rebuild affected binaries that include go/parser after upgrading the Go toolchain.
  • Limit parsing of untrusted Go source where immediate upgrading is delayed.
  • Check Go vendor guidance and vulnerability database entries for supported release details.

Validation and detection

  • Inventory Go versions used to build services, developer tools, and CI utilities.
  • Identify components that import or indirectly use go/parser on external input.
  • Confirm production binaries were rebuilt with a fixed Go release.
  • Review crash logs for parser-related stack exhaustion or unexpected panics.
Prepared
Confidence
high
Sources
6

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-1962 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/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
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2022-1962Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/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 librarygo/parsergo/parser, 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.