Service interruption via unbounded nesting and alias expansion
Published Dec 27, 2022 · Updated Apr 14, 2025
Resource exhaustion in gopkg.in/yaml.v2 before 2.2.4 allows attackers to interrupt consuming services via crafted YAML input. The scanner permits extremely deep flow and indentation nesting, while the decoder's permissive alias ratio drives nonlinear parsing and excessive allocations. Impact requires a consuming application to parse attacker-controlled YAML and is limited to CPU or memory exhaustion.
Summary
What happened
Resource exhaustion in gopkg.in/yaml.v2 before 2.2.4 allows attackers to interrupt consuming services via crafted YAML input. The scanner permits extremely deep flow and indentation nesting, while the decoder's permissive alias ratio drives nonlinear parsing and excessive allocations. Impact requires a consuming application to parse attacker-controlled YAML and is limited to CPU or memory exhaustion.
The record
- CVE
- CVE-2022-3064
- Published
- Dec 27, 2022
- Updated
- Apr 14, 2025
- Vendor
- go-yaml
- Product
- go-yaml/yaml
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 27, 2022CVE publishedPublication date reported by the CVE source.
- Apr 14, 2025Record 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 <2.2.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