Host memory exhaustion via unbounded ExecSync output
Published Jun 6, 2022 · Updated Aug 3, 2024
Uncontrolled resource consumption in containerd before 1.5.13 and 1.6.0 through 1.6.5 allows attackers to exhaust host memory. The CRI ExecSync handler accumulates container stdout and stderr in uncapped byte buffers before returning its response. A container command must be invoked through ExecSync and emit sustained output; exploitation interrupts containerd and other host workloads.
Summary
What happened
Uncontrolled resource consumption in containerd before 1.5.13 and 1.6.0 through 1.6.5 allows attackers to exhaust host memory. The CRI ExecSync handler accumulates container stdout and stderr in uncapped byte buffers before returning its response. A container command must be invoked through ExecSync and emit sustained output; exploitation interrupts containerd and other host workloads.
The record
- CVE
- CVE-2022-31030
- Published
- Jun 6, 2022
- Updated
- Aug 3, 2024
- Vendor
- containerd
- Product
- containerd
- Classifications
- CWE-400, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 6, 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=< 1.5.13
- Affected versionversion=>= 1.6.0, < 1.6.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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