LiveActive security incident?Get immediate response
CVE Record

CVE-2022-30633: Stack exhaustion when unmarshaling certain documents in encoding/xml

Uncontrolled recursion in Unmarshal in encoding/xml before Go 1.17.12 and Go 1.18.4 allows an attacker to cause a panic due to stack exhaustion via unmarshalling an XML document into a Go struct which has a nested field that uses the 'any' field tag.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw can let an attacker crash some Go applications by sending XML that triggers excessive recursion during parsing. The business impact is denial of service, not data theft or code execution, based on the provided sources.

Executive priority

Treat as a high-priority availability issue for internet-facing or partner-facing Go services that parse XML. Prioritize rebuilds with fixed Go versions where XML input can be attacker-controlled.

Technical view

CVE-2022-30633 is uncontrolled recursion in Go's encoding/xml.Unmarshal before Go 1.17.12 and 1.18.4. It affects unmarshalling XML into a Go struct with a nested field using the `any` tag, causing stack exhaustion and a panic.

Likely exposure

Exposure is most likely in Go services, APIs, workers, or tooling that parse untrusted XML using encoding/xml and the affected struct pattern. Systems that do not accept XML or do not use Go's encoding/xml are less likely exposed.

Exploitation context

The bundle marks KEV as false, and no provided source states active exploitation. The CVSS vector indicates remote, unauthenticated, low-complexity denial of service, but availability is the only listed impact.

Researcher notes

The affected condition is narrower than all XML parsing: the sources identify Unmarshal into a struct with a nested field using `any`. Validate reachability before escalating, and avoid assuming code execution or confidentiality impact.

Mitigation direction

  • Upgrade affected builds to Go 1.17.12, Go 1.18.4, or a later supported Go release.
  • Rebuild and redeploy Go binaries after upgrading the toolchain.
  • Review services that accept XML from users, partners, queues, or files.
  • Check vendor guidance if using embedded Go runtimes or packaged appliances.
  • Where upgrade is delayed, limit exposure of untrusted XML parsing paths.

Validation and detection

  • Inventory Go binaries and confirm the Go toolchain version used to build each one.
  • Search code for encoding/xml Unmarshal on externally supplied XML.
  • Review XML struct definitions for nested fields using the `any` tag.
  • Confirm deployed binaries were rebuilt after the fixed Go version was installed.
  • Check monitoring for unexplained Go panics in XML parsing paths.
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-30633 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-30633Attack 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/xmlencoding/xml, 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.