@iotwins ,@luyao201 ,@hejiancong557
issue处理注意事项:
1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.
影响性分析说明:
openEuler评分: (评分和向量)
受影响版本排查(受影响/不受影响):
1.master(1.1.6):
2.openEuler-20.03-LTS-SP4:
3.openEuler-22.03-LTS-SP3(1.1.6):
4.openEuler-22.03-LTS-SP4(1.1.6):
5.openEuler-24.03-LTS(1.1.6):
6.openEuler-24.03-LTS-Next(1.1.6):
7.openEuler-24.03-LTS-SP1(1.1.6):
8.openEuler-24.03-LTS-SP2(1.1.6):
修复是否涉及abi变化(是/否)：
1.master(1.1.6):
2.openEuler-20.03-LTS-SP4:
3.openEuler-22.03-LTS-SP3(1.1.6):
4.openEuler-22.03-LTS-SP4(1.1.6):
5.openEuler-24.03-LTS(1.1.6):
6.openEuler-24.03-LTS-Next(1.1.6):
7.openEuler-24.03-LTS-SP1(1.1.6):
8.openEuler-24.03-LTS-SP2(1.1.6):
原因说明：
1.master(1.1.6):
2.openEuler-20.03-LTS-SP4:
3.openEuler-22.03-LTS-SP3(1.1.6):
4.openEuler-22.03-LTS-SP4(1.1.6):
5.openEuler-24.03-LTS(1.1.6):
6.openEuler-24.03-LTS-Next(1.1.6):
7.openEuler-24.03-LTS-SP1(1.1.6):
8.openEuler-24.03-LTS-SP2(1.1.6):
原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如master版本分支受影响，那原因说明只能是受影响对应的原因之一!)：
| 分支状态 | 原因说明 |
|---|---|
| 受影响 | 正常修复 |
| 受影响 | 暂不修复-漏洞仍在分析中 |
| 受影响 | 暂不修复-暂无解决方案或补丁 |
| 受影响 | 暂不修复-待升级版本修复 |
| 受影响 | 不修复-超出修复范围 |
| 受影响 | 不修复-特殊原因导致不再修复 |
| 不受影响 | 不受影响-组件不存在 |
| 不受影响 | 不受影响-已有内置的内联控制或缓解措施 |
| 不受影响 | 不受影响-漏洞代码不能被攻击者触发 |
| 不受影响 | 不受影响-漏洞代码不在执行路径 |
| 不受影响 | 不受影响-漏洞代码不存在 |
issue处理具体操作请参考:
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142
说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址 补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1
一、漏洞信息
漏洞编号：CVE-2024-41110
漏洞归属组件：apptainer
漏洞归属的版本：1.1.6
CVSS评分：
BaseScore：9.9 Critical
Vector：CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
漏洞简述：
Moby is an open-source project created by Docker for software containerization. A security vulnerability has been detected in certain versions of Docker Engine, which could allow an attacker to bypass authorization plugins (AuthZ) under specific circumstances. The base likelihood of this being exploited is low.Using a specially-crafted API request, an Engine API client could make the daemon forward the request or response to an authorization plugin without the body. In certain circumstances, the authorization plugin may allow a request which it would have otherwise denied if the body had been forwarded to it.A security issue was discovered In 2018, where an attacker could bypass AuthZ plugins using a specially crafted API request. This could lead to unauthorized actions, including privilege escalation. Although this issue was fixed in Docker Engine v18.09.1 in January 2019, the fix was not carried forward to later major versions, resulting in a regression. Anyone who depends on authorization plugins that introspect the request and/or response body to make access control decisions is potentially impacted.Docker EE v19.03.x and all versions of Mirantis Container Runtime are not vulnerable.docker-ce v27.1.1 containes patches to fix the vulnerability. Patches have also been merged into the master, 19.03, 20.0, 23.0, 24.0, 25.0, 26.0, and 26.1 release branches. If one is unable to upgrade immediately, avoid using AuthZ plugins and/or restrict access to the Docker API to trusted parties, following the principle of least privilege.
漏洞公开时间：2024-07-25 01:15:11
漏洞创建时间：2025-05-30 07:41:36
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2024-41110
更多参考(点击展开)
漏洞分析指导链接：
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
其他
漏洞补丁信息：
详情(点击展开)
二、漏洞分析结构反馈
影响性分析说明：
openEuler评分：
9.9
Vector：CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
受影响版本排查(受影响/不受影响)：
1.master(1.1.6):
2.openEuler-20.03-LTS-SP4:
3.openEuler-22.03-LTS-SP3(1.1.6):
4.openEuler-22.03-LTS-SP4(1.1.6):
5.openEuler-24.03-LTS(1.1.6):
6.openEuler-24.03-LTS-Next(1.1.6):
7.openEuler-24.03-LTS-SP1(1.1.6):
8.openEuler-24.03-LTS-SP2(1.1.6):
修复是否涉及abi变化(是/否)：
1.master(1.1.6):
2.openEuler-20.03-LTS-SP4:
3.openEuler-22.03-LTS-SP3(1.1.6):
4.openEuler-22.03-LTS-SP4(1.1.6):
5.openEuler-24.03-LTS(1.1.6):
6.openEuler-24.03-LTS-Next(1.1.6):
7.openEuler-24.03-LTS-SP1(1.1.6):
8.openEuler-24.03-LTS-SP2(1.1.6):
原因说明：
1.master(1.1.6):
2.openEuler-20.03-LTS-SP4:
3.openEuler-22.03-LTS-SP3(1.1.6):
4.openEuler-22.03-LTS-SP4(1.1.6):
5.openEuler-24.03-LTS(1.1.6):
6.openEuler-24.03-LTS-Next(1.1.6):
7.openEuler-24.03-LTS-SP1(1.1.6):
8.openEuler-24.03-LTS-SP2(1.1.6):