Service interruption via FIPS TLS memory leak
Published Jan 10, 2022 · Updated Aug 3, 2024
A memory leak in Mirantis Container Runtime 20.10.8 allows remote attackers to interrupt service through TLS handshakes. The FIPS-enabled TLS handshake path fails to release memory consumed while processing handshakes, although Mirantis has not identified the affected function or allocation. FIPS mode is not enabled by default, and repeated unauthenticated handshakes can progressively exhaust runtime memory and degrade or halt service.
Summary
What happened
A memory leak in Mirantis Container Runtime 20.10.8 allows remote attackers to interrupt service through TLS handshakes. The FIPS-enabled TLS handshake path fails to release memory consumed while processing handshakes, although Mirantis has not identified the affected function or allocation. FIPS mode is not enabled by default, and repeated unauthenticated handshakes can progressively exhaust runtime memory and degrade or halt service.
The record
- CVE
- CVE-2021-23218
- Published
- Jan 10, 2022
- Updated
- Aug 3, 2024
- Vendor
- Mirantis
- Product
- Mirantis Container Runtime
- Classifications
- CWE-401, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 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=20.10.8
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