-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
配置cve-2020-15257的小问题 #74
Comments
|
…ch could be helpful for #74 temporarily
@duowen1 关于runc和docker-runc的问题,经测试在contrainerd安装成功(cnv install cve-2020-15257)后,runc、docker-runc均存在,路径分别为/usr/sbin/runc和/usr/bin/docker-runc,我这边用CDK去测试反弹shell是没有问题的。 |
This issue will be closed. However the installation problem of containerd has not been solved perfectly yet. If necessary, someone may reopen this issue and we will talk and figure out how to solve it :p |
在Ubuntu18.04和16.04分别搭建过环境,最后结果都下面所示,Linux内核版本是5.8.0-59-generic
安装成功,但是显示有warning
然后按照Writeup的方式去复现,可以找到抽象命名空间的套接字。但是在进行exploit时发现结果如下所示:
报错信息显示runc不在PATH路径下,执行runc提示需要安装。发现实际上安装的runc可执行文件为docker-runc,创建软链接后利用成功。
似乎如果系统安装过docker,再利用metarget安装漏洞环境就会导致runc的名称问题。不知道这属不属于bug,或许在writeup上可以做下标注?
The text was updated successfully, but these errors were encountered: