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
Vulnerability: CVE-2021-3973, Vim #1408
Comments
We can just remove |
Yes, it has been a while since I looked at the Dockerfiles and I had forgotten that we were specifically installing vim. I guess we might have installed it for debugging purposes. I was expecting that it was being installed with the base OS and would need to be removed instead. @jonespm, thanks for moving this to "in progress" for me. I was just about to do that. |
To address vulnerability CVE-2021-3973, remove Vim, which was probably installed for debugging purposes.
Duelling linked pull requests! 20 paces, at dawn! 😉 |
As specified in #1408, to address vulnerability CVE-2021-3973, remove Vim, which was probably installed for debugging purposes.
As specified in tl-its-umich-edu#1408, to address vulnerability CVE-2021-3973, remove Vim, which was probably installed for debugging purposes.
From vulnerabilities spreadsheet, based on Unizin analysis:
According to discussions, because MyLA doesn't need Vim, the best resolution for this vulnerability would be to remove Vim from the MyLA images. This could be accomplished by explicitly removing Vim in the
Dockerfile
.The text was updated successfully, but these errors were encountered: