Allocation of Resources Without Limits or Throttling Affecting podman package, versions <2:4.0.2-8.module+el8.7.0+16520+2db5507d
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-CENTOS8-PODMAN-3107889
- published 7 Jun 2022
- disclosed 6 Jun 2022
Introduced: 6 Jun 2022
CVE-2022-1708 Open this link in a new tabHow to fix?
Upgrade Centos:8 podman to version 2:4.0.2-8.module+el8.7.0+16520+2db5507d or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream podman package and not the podman package as distributed by Centos.
See How to fix? for Centos:8 relevant fixed versions and status.
A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to the Kube API. The ExecSync request runs commands in a container and logs the output of the command. This output is then read by CRI-O after command execution, and it is read in a manner where the entire file corresponding to the output of the command is read in. Thus, if the output of the command is large it is possible to exhaust the memory or the disk space of the node when CRI-O reads the output of the command. The highest threat from this vulnerability is system availability.
References
- https://access.redhat.com/security/cve/CVE-2022-1708
- https://access.redhat.com/errata/RHSA-2022:7469
- https://bugzilla.redhat.com/show_bug.cgi?id=2085361
- https://github.com/cri-o/cri-o/commit/f032cf649ecc7e0c46718bd9e7814bfb317cb544
- https://github.com/cri-o/cri-o/security/advisories/GHSA-fcm2-6c3h-pg6j