Application crash via unbounded ignored-field recursion
Published Aug 9, 2022 · Updated Mar 6, 2026
Uncontrolled recursion in Go encoding/gob before 1.17.12 and 1.18.0 through 1.18.3 allows remote attackers to crash applications. Decoder.decIgnoreOpFor and related decoder compilation paths recursively descend nested ignored fields without a depth limit, exhausting the process stack and causing a panic. A reachable application must pass an attacker-controlled gob stream to Decoder.Decode; the resulting panic interrupts that process without reported data disclosure or modification.
Summary
What happened
Uncontrolled recursion in Go encoding/gob before 1.17.12 and 1.18.0 through 1.18.3 allows remote attackers to crash applications. Decoder.decIgnoreOpFor and related decoder compilation paths recursively descend nested ignored fields without a depth limit, exhausting the process stack and causing a panic. A reachable application must pass an attacker-controlled gob stream to Decoder.Decode; the resulting panic interrupts that process without reported data disclosure or modification.
The record
- CVE
- CVE-2022-30635
- Published
- Aug 9, 2022
- Updated
- Mar 6, 2026
- Vendor
- Go standard library
- Product
- encoding/gob
- Classifications
- CWE-674, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 9, 2022CVE publishedPublication date reported by the CVE source.
- Mar 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.17.12
- Affected versionversion=1.18.0-0 <1.18.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo