ALBA-2020:2457 container-tools:2.0 bug fix update
Not scored
Published
Check this codebase for ALBA-2020:2457 and fix it if it is affected.
What it is: ALBA-2020:2457 is a vulnerability in cockpit-podman, published on 9 Jun 2020.
Exploitation: There is no known exploitation of ALBA-2020:2457 in the wild and no public exploit code.
Affected product: cockpit-podman. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/ALBA-2020-2457/ (Markdown: https://insights.sbomify.com/ALBA-2020-2457/index.md)
Bug fix update for container tools including podman, buildah, skopeo, and runc to correct native container healthchecks.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- Available
What is ALBA-2020:2457?
ALBA-2020:2457 is a vulnerability in cockpit-podman, published on 9 Jun 2020.
Official description
The container-tools module contains tools for working with containers, notably podman, buildah, skopeo, and runc.
Bug Fix(es):
- podman: Please backport correction patch for the native container healthchecks (BZ#1836978)
Which versions are affected by ALBA-2020:2457?
Linux distribution packages (21)
cockpit-podman AlmaLinux:8 | All versions | 11-1.module_el8.5.0+108+00865455 |
cockpit-podman AlmaLinux:8 | All versions | 11-1.module_el8.5.0+2635+e4386a39 |
containernetworking-plugins AlmaLinux:8 | All versions | 0.8.3-4.module_el8.5.0+108+00865455 |
containernetworking-plugins AlmaLinux:8 | All versions | 0.8.3-4.module_el8.5.0+2635+e4386a39 |
crit AlmaLinux:8 | All versions | 3.12-9.module_el8.3.0+2044+12421f43 |
crit AlmaLinux:8 | All versions | 3.12-9.module_el8.4.0+2496+12421f43 |
crit AlmaLinux:8 | All versions | 3.12-9.module_el8.5.0+119+9a9ec082 |
criu AlmaLinux:8 | All versions | 3.12-9.module_el8.3.0+2044+12421f43 |
criu AlmaLinux:8 | All versions | 3.12-9.module_el8.4.0+2496+12421f43 |
criu AlmaLinux:8 | All versions | 3.12-9.module_el8.5.0+119+9a9ec082 |
python-podman-api AlmaLinux:8 | All versions | 1.2.0-0.2.gitd0a45fe.module_el8.5.0+108+00865455 |
python-podman-api AlmaLinux:8 | All versions | 1.2.0-0.2.gitd0a45fe.module_el8.5.0+2635+e4386a39 |
python3-criu AlmaLinux:8 | All versions | 3.12-9.module_el8.3.0+2044+12421f43 |
python3-criu AlmaLinux:8 | All versions | 3.12-9.module_el8.4.0+2496+12421f43 |
python3-criu AlmaLinux:8 | All versions | 3.12-9.module_el8.5.0+119+9a9ec082 |
slirp4netns AlmaLinux:8 | All versions | 0.4.2-3.git21fdece.module_el8.5.0+108+00865455 |
slirp4netns AlmaLinux:8 | All versions | 0.4.2-3.git21fdece.module_el8.5.0+2635+e4386a39 |
toolbox AlmaLinux:8 | All versions | 0.0.7-1.module_el8.5.0+108+00865455 |
toolbox AlmaLinux:8 | All versions | 0.0.7-1.module_el8.5.0+2635+e4386a39 |
udica AlmaLinux:8 | All versions | 0.2.1-2.module_el8.5.0+108+00865455 |
udica AlmaLinux:8 | All versions | 0.2.1-2.module_el8.5.0+2635+e4386a39 |
How do I fix ALBA-2020:2457?
Upgrade to a fixed version.
Is ALBA-2020:2457 being exploited?
There is no known exploitation of ALBA-2020:2457 in the wild and no public exploit code.