一、漏洞信息
漏洞编号:CVE-2020-15157
漏洞归属组件:containerd
漏洞归属的版本:1.2.0
CVSS V3.0分值:
BaseScore:6.1 Medium
Vector:CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N
漏洞简述:
In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the users username and password for the registry. In other cases, this may be the credentials attached to the cloud virtual instance which can grant access to other cloud resources in the account. The default containerd resolver is used by the cri-containerd plugin (which can be used by Kubernetes), the ctr development tool, and other client programs that have explicitly linked against it. This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected. If you are using containerd 1.3 or later, you are not affected. If you are using cri-containerd in the 1.2 series or prior, you should ensure you only pull images from trusted sources. Other container runtimes built on top of containerd but not using the default resolver (such as Docker) are not affected.
漏洞公开时间:
漏洞创建时间:2021-02-24 17:16:30
漏洞详情参考链接:
https://nvd.nist.gov/vuln/detail/CVE-2020-15157
漏洞分析指导链接:
https://gitee.com/openeuler/cve-manager/blob/master/doc/md/manual.md
二、漏洞分析结构反馈
影响性分析说明:
使用docker调用containerd的场景不涉及
openEuler评分:
6.1
Vector:CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N
受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS:不受影响
2.openEuler-20.03-LTS-SP1:不受影响
3.openEuler-20.09:不受影响
@haomintsai ,@lifeng_isula ,@haozi007 ,@LeonZhang ,@flyflyflypeng
issue处理注意事项:
1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容, 否则无法关闭当前issue;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响))不能省略,省略后cve-manager将无法正常解析填写内容.
影响性分析说明:
openEuler评分: (评分和向量)
受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS:
2.openEuler-20.03-LTS-SP1:
3.openEuler-20.09:
issue处理具体操作请参考:
https://gitee.com/openeuler/cve-manager/blob/master/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。
Hey openeuler-ci-bot, Welcome to openEuler Community.
All of the projects in openEuler Community are maintained by @openeuler-ci-bot.
That means the developers can comment below every pull request or issue to trigger Bot Commands.
Please follow instructions at https://gitee.com/openeuler/community/blob/master/en/sig-infrastructure/command.md to find the details.
影响性分析说明:使用docker调用containerd的场景不涉及
openEuler评分: 6.1
受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS:不受影响
2.openEuler-20.03-LTS-SP1:不受影响
3.openEuler-20.09:不受影响
@haomintsai 经过 cve-manager 解析, 已分析的内容如下表所示:
状态 | 需分析 | 内容 |
---|---|---|
已分析 | 影响性分析说明 | 使用docker调用containerd的场景不涉及 |
已分析 | openEulerScore | 6.1 |
已分析 | openEulerVector | AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N |
已分析 | 受影响版本排查 | openEuler-20.03-LTS:不受影响,openEuler-20.03-LTS-SP1:不受影响,openEuler-20.09:不受影响 |
请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.
登录 后才可以发表评论