Bug 2315691 (CVE-2024-9341)
| Summary: | CVE-2024-9341 Podman: Buildah: cri-o: FIPS Crypto-Policy Directory Mounting Issue in containers/common Go Library | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability | Assignee: | Product Security DevOps Team <prodsec-dev> |
| Status: | NEW --- | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | asdas, bmontgom, dpaolell, eparis, jburrell, jdelft, jupierce, lgarciaa, mbiarnes, nstielau, security-response-team, sidsharm, sponnaga, talessio, vlaad, ximhan, yuxzhu |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: |
A flaw was found in Go. When FIPS mode is enabled on a system, container runtimes may incorrectly handle certain file paths due to improper validation in the containers/common Go library. This flaw allows an attacker to exploit symbolic links and trick the system into mounting sensitive host directories inside a container. This issue also allows attackers to access critical host files, bypassing the intended isolation between containers and the host system.
|
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: | 2318512, 2318511, 2318513, 2318514 | ||
| Bug Blocks: | |||
| Deadline: | 2024-10-01 | ||
|
Description
OSIDB Bzimport
2024-09-30 15:47:51 UTC
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:8039 https://access.redhat.com/errata/RHSA-2024:8039 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:8112 https://access.redhat.com/errata/RHSA-2024:8112 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.17 Via RHSA-2024:7925 https://access.redhat.com/errata/RHSA-2024:7925 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.14 Via RHSA-2024:8238 https://access.redhat.com/errata/RHSA-2024:8238 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.16 Via RHSA-2024:8263 https://access.redhat.com/errata/RHSA-2024:8263 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.15 Via RHSA-2024:8428 https://access.redhat.com/errata/RHSA-2024:8428 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:8846 https://access.redhat.com/errata/RHSA-2024:8846 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.13 Via RHSA-2024:8690 https://access.redhat.com/errata/RHSA-2024:8690 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.12 Ironic content for Red Hat OpenShift Container Platform 4.12 Via RHSA-2024:8694 https://access.redhat.com/errata/RHSA-2024:8694 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:9454 https://access.redhat.com/errata/RHSA-2024:9454 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:9459 https://access.redhat.com/errata/RHSA-2024:9459 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.16 Via RHSA-2024:10147 https://access.redhat.com/errata/RHSA-2024:10147 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.17 Via RHSA-2024:10818 https://access.redhat.com/errata/RHSA-2024:10818 |