目标达成 感谢每一位支持者 — 我们达成了 100% 目标！

目标: 1000 元 · 已筹: 1359 元

100%
请我们喝杯咖啡

CVE-2020-15157— containerd 安全漏洞

一分钟漏洞结论

影响对象
containerd containerd
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。

containerd是美国阿帕奇（Apache）软件基金会的一个容器守护进程。该进程根据 RunC OCI 规范负责控制宿主机上容器的完整周期。 containerd (an industry-standard container runtime) 1.2.14之前版本存在安全漏洞，该漏洞源于存在一个凭据泄漏漏洞，如果URL所在的服务器显示HTTP 401状态码以及注册特定的状态码，默认的containerd解析器将提供其身份验证凭据。

CVSS 6.1 · Medium EPSS 2.30% · P83
获取后续新漏洞提醒 登录后订阅

一、 漏洞 CVE-2020-15157 基础信息

漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗

尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。

Vulnerability Title
containerd can be coerced into leaking credentials during image pull
来源: CVE Program / CVE List V5
Vulnerability Description
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 user's 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.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N
来源: CVE Program / CVE List V5
Vulnerability Type
不充分的凭证保护机制
来源: CVE Program / CVE List V5
Vulnerability Title
containerd 安全漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
containerd是美国阿帕奇（Apache）软件基金会的一个容器守护进程。该进程根据 RunC OCI 规范负责控制宿主机上容器的完整周期。 containerd (an industry-standard container runtime) 1.2.14之前版本存在安全漏洞，该漏洞源于存在一个凭据泄漏漏洞，如果URL所在的服务器显示HTTP 401状态码以及注册特定的状态码，默认的containerd解析器将提供其身份验证凭据。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD

受影响产品

厂商 产品 影响版本 CPE 订阅
containerd containerd < 1.2.14 -

二、漏洞 CVE-2020-15157 的公开POC

# POC 描述 源链接 神龙链接
AI 生成 POC 高级

未找到公开 POC。

登录以生成 AI POC

三、漏洞 CVE-2020-15157 的情报信息

请登录查看更多情报信息。

CVE-2020-15157 厂商安全公告 (4)

CVE-2020-15157 其他参考 (1)

IV. Related Vulnerabilities

Same product: containerd
Same vendor: containerd
Same weakness: CWE-522

V. Comments for CVE-2020-15157

暂无评论

发表评论