CVE-2024-45310

一、漏洞信息
 漏洞编号：[CVE-2024-45310](https://nvd.nist.gov/vuln/detail/CVE-2024-45310)
 漏洞归属组件：[buildah](https://gitee.com/src-openeuler/buildah)
 漏洞归属的版本：1.26.1,1.34.1
 CVSS V3.0分值：
  BaseScore：3.6 Low
  Vector：CVSS：3.0/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N
 漏洞简述：
  runc is a CLI tool for spawning and running containers according to the OCI specification. runc 1.1.13 and earlier, as well as 1.2.0-rc2 and earlier, can be tricked into creating empty files or directories in arbitrary locations in the host filesystem by sharing a volume between two containers and exploiting a race with `os.MkdirAll`. While this could be used to create empty files, existing files would not be truncated. An attacker must have the ability to start containers using some kind of custom volume configuration. Containers using user namespaces are still affected, but the scope of places an attacker can create inodes can be significantly reduced. Sufficiently strict LSM policies (SELinux/Apparmor) can also in principle block this attack -- we suspect the industry standard SELinux policy may restrict this attack s scope but the exact scope of protection hasn t been analysed. This is exploitable using runc directly as well as through Docker and Kubernetes. The issue is fixed in runc v1.1.14 and v1.2.0-rc3.Some workarounds are available. Using user namespaces restricts this attack fairly significantly such that the attacker can only create inodes in directories that the remapped root user/group has write access to. Unless the root user is remapped to an actualuser on the host (such as with rootless containers that don t use `/etc/sub[ug]id`), this in practice means that an attacker would only be able to create inodes in world-writable directories. A strict enough SELinux or AppArmor policy could in principle also restrict the scope if a specific label is applied to the runc runtime, though neither the extent to which the standard existing policies block this attack nor what exact policies are needed to sufficiently restrict this attack have been thoroughly tested.
 漏洞公开时间：2024-09-04 03:15:15
 漏洞创建时间：2025-06-20 13:58:50
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-45310
<details>
<summary>更多参考(点击展开)</summary>

无
</details>

漏洞分析指导链接：
  https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
  其他
 漏洞补丁信息：
  <details>
<summary>详情(点击展开)</summary>

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| opencontainers/runc |  | https://github.com/opencontainers/runc/commit/63c2908164f3a1daea455bf5bcd8d363d70328c7.patch |  | ljqc |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
                          
 openEuler评分：
  3.6
 Vector：CVSS：3.0/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N
 受影响版本排查(受影响/不受影响)：
  1.master:
2.openEuler-20.03-LTS-SP4:
3.openEuler-22.03-LTS-SP3:
4.openEuler-22.03-LTS-SP4:
5.openEuler-24.03-LTS(1.34.1):
6.openEuler-24.03-LTS-Next(1.34.1):
7.openEuler-24.03-LTS-SP1(1.34.1):
8.openEuler-24.03-LTS-SP2(1.34.1):

修复是否涉及abi变化(是/否)：
  1.master:
2.openEuler-20.03-LTS-SP4:
3.openEuler-22.03-LTS-SP3:
4.openEuler-22.03-LTS-SP4:
5.openEuler-24.03-LTS(1.34.1):
6.openEuler-24.03-LTS-Next(1.34.1):
7.openEuler-24.03-LTS-SP1(1.34.1):
8.openEuler-24.03-LTS-SP2(1.34.1):

原因说明：
  1.master:
2.openEuler-20.03-LTS-SP4:
3.openEuler-22.03-LTS-SP3:
4.openEuler-22.03-LTS-SP4:
5.openEuler-24.03-LTS(1.34.1):
6.openEuler-24.03-LTS-Next(1.34.1):
7.openEuler-24.03-LTS-SP1(1.34.1):
8.openEuler-24.03-LTS-SP2(1.34.1):

src-openEuler/buildah

Content Risk Flag

Comments (3)

src-openEuler/buildah .gitee-modal { width: 500px !important; }

Content Risk Flag

CVE-2024-45310

Comments (3)

Search

src-openEuler/buildah