Skip to content
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

Use of GOSU introduces critical CVEs #1248

Closed
matt-gribben opened this issue Jun 18, 2024 · 2 comments
Closed

Use of GOSU introduces critical CVEs #1248

matt-gribben opened this issue Jun 18, 2024 · 2 comments

Comments

@matt-gribben
Copy link

The use of GOSU introduces critical vulnerabilities that mean this image can't be used in many production environments. The cause is that the current release of GOSU uses Go 1.18.2 and these issues were fixed in 1.19.9

Two of these are 9.8s
[CVE-2023-24540⁠]
[CVE-2023-24538⁠]

This version also causes alerts for another 29 High vulnerabilities in tools like docker scout etc.

@yosifkit
Copy link
Member

gosu is not vulnerable to those CVEs: https://github.com/tianon/gosu/blob/master/SECURITY.md. See also tianon/gosu#136 (comment). TLDR: the industry can and should do better than just spout out perceived CVE's and instead use the available data to see whether they are applicable or not (like govulncheck).

@matt-gribben
Copy link
Author

@yosifkit I'm aware that it isn't actually vulnerable to those CVEs but that doesn't change the fact I can't deploy something that's being flagged for critical CVEs. Yes the industry should do better, but the right here and now means this is an issue. IMO

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants