Application crash via recursive XML element skipping
Published Aug 9, 2022 · Updated Aug 3, 2024
Uncontrolled recursion in Go encoding/xml before 1.17.12 and 1.18.0 through 1.18.3 allows attackers to crash applications via nested XML. Decoder.Skip calls itself for every nested start element instead of tracking nesting depth iteratively, eventually exhausting the goroutine stack. Reachability requires an application to invoke Decoder.Skip on attacker-controlled, deeply nested XML; the resulting panic interrupts that application process.
Summary
What happened
Uncontrolled recursion in Go encoding/xml before 1.17.12 and 1.18.0 through 1.18.3 allows attackers to crash applications via nested XML. Decoder.Skip calls itself for every nested start element instead of tracking nesting depth iteratively, eventually exhausting the goroutine stack. Reachability requires an application to invoke Decoder.Skip on attacker-controlled, deeply nested XML; the resulting panic interrupts that application process.
The record
- CVE
- CVE-2022-28131
- Published
- Aug 9, 2022
- Updated
- Aug 3, 2024
- Vendor
- Go standard library
- Product
- encoding/xml
- Classifications
- CWE-674, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 9, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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