Open Source Vulnerability in container-tools:rhel8
Summary
ALBA-2020:2456: container-tools:rhel8 bug fix update. Affects crit across 3 version ranges.
< 3.12-9.module_el8.3.0+2044+12421f43
< 3.12-9.module_el8.4.0+2496+12421f43
< 3.12-9.module_el8.5.0+119+9a9ec082
Fixed in 3.12-9.module_el8.3.0+2044+12421f43, 3.12-9.module_el8.4.0+2496+12421f43 or 3.12-9.module_el8.5.0+119+9a9ec082, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The container-tools module is a collection of tools used for working with containers, including podman, buildah, skopeo, and runc. These tools are commonly used in containerized environments to manage and interact with containers. The vulnerability affects the container-tools module in the RHEL 8 distribution.
Vulnerability Detail
The vulnerability in container-tools:rhel8 is related to native container healthchecks in podman. The specific issue is described in bug BZ#1834346. The vulnerability could potentially lead to incorrect behavior or failure of container healthchecks, impacting the reliability and stability of containerized applications.
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
sudo dnf update crit-
< 3.12-9.module_el8.3.0+2044+12421f433.12-9.module_el8.3.0+2044+12421f43 -
< 3.12-9.module_el8.4.0+2496+12421f433.12-9.module_el8.4.0+2496+12421f43 -
< 3.12-9.module_el8.5.0+119+9a9ec0823.12-9.module_el8.5.0+119+9a9ec082
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. It is recommended to apply the fix by updating the affected packages.
Conclusion
The vulnerability in container-tools:rhel8 related to native container healthchecks can impact the reliability and stability of containerized applications. It is recommended to update the affected packages to the fixed versions mentioned above. If you have any further questions or need assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for crit →
FAQ
The vulnerability can result in incorrect behavior or failure of container healthchecks, affecting the reliability and stability of containerized applications.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and it will analyze and alert you if the vulnerability is present.
There are no known exploits for this vulnerability at the moment. However, it is recommended to apply the fix as soon as possible to mitigate any potential risks.
It is not recommended to manually fix this vulnerability without updating the packages. The fix provided in the updated packages addresses the specific issue and ensures the proper functioning of container healthchecks.
You can find more information about this vulnerability in the AlmaLinux OSV Database advisory: https://github.com/AlmaLinux/osv-database/blob/master/advisories/almalinux8/ALBA-2020:2456.json
References
Related vulnerabilities
Recent vulnerabilities recorded for crit.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
