Bug 2258725 (CVE-2024-21626, Leaky-Vessels)
| Summary: | CVE-2024-21626 runc: file descriptor leak | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Avinash Hanwate <ahanwate> |
| Component: | vulnerability | Assignee: | Product Security <prodsec-ir-bot> |
| Status: | NEW --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | apjagtap, asatyam, bdettelb, broose, caswilli, dfreiber, diagrawa, dornelas, drow, gandhi.srini, hkataria, jburrell, jpriddy, jsherril, kaycoth, kshier, luizcosta, nweather, rogbas, sabiswas, security-response-team, stcannon, tsweeney, vkumar, yguenane, ymittal |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | runc 1.1.12 | Doc Type: | If docs needed, set a value |
| Doc Text: |
A file descriptor leak issue was found in the runc package. While a user performs `O_CLOEXEC` all file descriptors before executing the container code, the file descriptor is open when performing `setcwd(2)`, which means that the reference can be kept alive in the container by configuring the working directory to be a path resolved through the file descriptor. The non-dumpable bit is unset after `execve`, meaning there are multiple ways to attack this other than bad configurations. The only way to defend against it entirely is to close all unneeded file descriptors.
|
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: | 2262166 | ||
| Bug Blocks: | 2258742 | ||
|
Description
Avinash Hanwate
2024-01-17 05:00:08 UTC
Created runc tracking bugs for this issue: Affects: fedora-all [bug 2262166] This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:0670 https://access.redhat.com/errata/RHSA-2024:0670 This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Extras Via RHSA-2024:0717 https://access.redhat.com/errata/RHSA-2024:0717 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.0 Extended Update Support Via RHSA-2024:0756 https://access.redhat.com/errata/RHSA-2024:0756 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:0748 https://access.redhat.com/errata/RHSA-2024:0748 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:0752 https://access.redhat.com/errata/RHSA-2024:0752 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Extended Update Support Via RHSA-2024:0755 https://access.redhat.com/errata/RHSA-2024:0755 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions Red Hat Enterprise Linux 8.4 Telecommunications Update Service Via RHSA-2024:0760 https://access.redhat.com/errata/RHSA-2024:0760 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Extended Update Support Via RHSA-2024:0757 https://access.redhat.com/errata/RHSA-2024:0757 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Extended Update Support Via RHSA-2024:0759 https://access.redhat.com/errata/RHSA-2024:0759 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.2 Advanced Update Support Red Hat Enterprise Linux 8.2 Update Services for SAP Solutions Red Hat Enterprise Linux 8.2 Telecommunications Update Service Via RHSA-2024:0758 https://access.redhat.com/errata/RHSA-2024:0758 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.11 Via RHSA-2024:0682 https://access.redhat.com/errata/RHSA-2024:0682 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.13 Via RHSA-2024:0662 https://access.redhat.com/errata/RHSA-2024:0662 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.11 Via RHSA-2024:0684 https://access.redhat.com/errata/RHSA-2024:0684 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.14 Via RHSA-2024:0645 https://access.redhat.com/errata/RHSA-2024:0645 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.12 Via RHSA-2024:0666 https://access.redhat.com/errata/RHSA-2024:0666 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Extended Update Support Via RHSA-2024:0764 https://access.redhat.com/errata/RHSA-2024:0764 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.15 Via RHSA-2023:7201 https://access.redhat.com/errata/RHSA-2023:7201 This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Extras Via RHSA-2024:1270 https://access.redhat.com/errata/RHSA-2024:1270 Hi All, Seeing this vulnerability reported against the package "github.com/opencontainers/runc" which is bundled with either RedHat 8.9 minimial or OSE. Looking for a fix at the earliest as it is blocking our monthly release. Thanks & Regards, Gandhi. IBM MQ Container - Security Lead. |