Bug 2372501 (CVE-2025-6032)
| Summary: | CVE-2025-6032 podman: podman missing TLS verification | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability | Assignee: | Product Security DevOps Team <prodsec-dev> |
| Status: | NEW --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | cevich, ddarrah, dshea, gsuckevi, jhonce, jnovy, mheon, pholzing, security-response-team, tsweeney, vnaruka, ypu |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: |
A flaw was found in Podman. The podman machine init command fails to verify the TLS certificate when downloading the VM images from an OCI registry. This issue results in a Man In The Middle attack.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2374581 | ||
| Bug Blocks: | |||
| Deadline: | 2025-06-24 | ||
|
Description
OSIDB Bzimport
2025-06-12 15:24:27 UTC
Just noting that the code with the issue was first introduced in Podman v4.8 and RHEL 8.10 & 9.4. Also in OCP 4.16. Earlier versions of OCP and RHEL are not affected by this issue. This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.19 Via RHSA-2025:9751 https://access.redhat.com/errata/RHSA-2025:9751 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.18 Via RHSA-2025:9726 https://access.redhat.com/errata/RHSA-2025:9726 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.16 Via RHSA-2025:9766 https://access.redhat.com/errata/RHSA-2025:9766 This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2025:10549 https://access.redhat.com/errata/RHSA-2025:10549 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2025:10550 https://access.redhat.com/errata/RHSA-2025:10550 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2025:10551 https://access.redhat.com/errata/RHSA-2025:10551 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Extended Update Support Via RHSA-2025:10668 https://access.redhat.com/errata/RHSA-2025:10668 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.17 Via RHSA-2025:10295 https://access.redhat.com/errata/RHSA-2025:10295 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.19 Via RHSA-2025:11363 https://access.redhat.com/errata/RHSA-2025:11363 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.17 Via RHSA-2025:11359 https://access.redhat.com/errata/RHSA-2025:11359 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.16 Via RHSA-2025:11681 https://access.redhat.com/errata/RHSA-2025:11681 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.18 Via RHSA-2025:11677 https://access.redhat.com/errata/RHSA-2025:11677 |