here's a vulnerability in the CRI-O application where when container is launched with securityContext.runAsUser specifying a non-existent user, CRI-O attempts to create the user, reading the container's entire /etc/passwd file into memory. If this file is excessively large, it can cause the a high memory consumption leading applications to be killed due to out-of-memory. As a result a denial-of-service can be achieved, possibly disrupting other pods and services running in the same host.
No configuration.
20 Aug 2025, 14:39
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Published : 2025-08-20 13:15
Updated : 2025-08-20 14:39
NVD link : CVE-2025-4437
Mitre link : CVE-2025-4437
CVE.ORG link : CVE-2025-4437
JSON object : View
No product.
Allocation of Resources Without Limits or Throttling