Node denial of service via unbounded ExecSync output
Published Jun 7, 2022 · Updated Aug 3, 2024
Denial of service in CRI-O 1.24.0 and earlier allows remote attackers with Kube API access to exhaust node memory or disk via ExecSync. CRI-O reads the entire command-output file after execution, so a container command producing unbounded output consumes node memory and logged disk space. Access to the Kubernetes API and permission to invoke ExecSync are required; the resulting impact is node service interruption without reported confidentiality or integrity loss.
Summary
What happened
Denial of service in CRI-O 1.24.0 and earlier allows remote attackers with Kube API access to exhaust node memory or disk via ExecSync. CRI-O reads the entire command-output file after execution, so a container command producing unbounded output consumes node memory and logged disk space. Access to the Kubernetes API and permission to invoke ExecSync are required; the resulting impact is node service interruption without reported confidentiality or integrity loss.
The record
- CVE
- CVE-2022-1708
- Published
- Jun 7, 2022
- Updated
- Aug 3, 2024
- Vendor
- CRI-O
- Product
- CRI-O
- Classifications
- CWE-770, CWE-400, T1499.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 7, 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=Affects cri-o <= 1.24.0, 1.23.2, 1.22.4, Fixed-in 1.24.1, 1.23.3, 1.22.5
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.
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