-
Notifications
You must be signed in to change notification settings - Fork 959
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
Docker Runner v2.300.0 has 1 critical and 6 high severity CVEs #2327
Comments
Almost all of these vulnerabilities (except |
inspried by actions/runner#2327
Hi @TingluoHuang is this being addressed? Fixing the CVE's should be fixed regardless of the suggested solutions.. Is there an intent to implement something like the suggested solution here? Should not be very hard to add to the repository. Additionally - is this something you want contributions for, or work out internally? |
In the most recent version,
None of the previous CVEs were mitigated. |
It looks like most, if not all, of the NPM vulnerabilities are not an issue. Either they were false-positives or they've been fixed, because I don't see any reference to And, while So, unless I missed something, I think it's safe to ignore those JS CVEs. |
@mario-campos Even if they are false positives though, every GitHub consumer running their own self-hosted GitHub runners will run into these same issues. Even the most recent version 2.309.0 has 4 CVEs, all in .NET: the same 3 as originally reported here 9 months ago, and additionally CVE-2019-0820 (HIGH severity, from
All of these CVEs seem mitigable simply by bumping version numbers. Doing so would absolve all GitHub consumers attempting to run self-hosted runners from investigating these same CVEs, which aggregated across all of us is currently a huge and unproductive time drain. |
I can't believe this is still an issue |
Still an issue - it gets tiresome seeing these pop up in vuln scanning |
Describe the bug
The GitHub Runner versions
2.299.1
and2.300.0
(most recent versions at the time of writing) have 1 critical severity and 6 high severity CVEs found by Trivy security vulnerability scan.To Reproduce
Steps to reproduce the behavior:
github-runner
, have the followingDockerfile
:entrypoint.sh
omitted for simplicity.Expected behavior
Expected zero HIGH or CRITICAL severity known, mitigatable vulnerabilities.
Runner Version and Platform
The GitHub-hosted runner generating the docker image and running the trivy scan:
The (to be self-hosted) runner Docker image being generated, which has vulnerabilities:
What's not working?
The Trivy vulnerability scan seems to indicate that the GitHub Runner code being pulled in via the Dockerfile is vulnerable to the following known CVEs:
json-schema
viapackage.json
)minimatch
viapackage.json
)npm
viapackage.json
)qs
viapackage.json
)dotnet-core
)dotnet-core
)dotnet-core
)Job Log Output
The full run log: trivy_run_redacted.log.
See in particular:
Suggested solution
Implement automated vulnerability scans of your own GitHub Runner code, and ensure any CRITICAL or HIGH severity CVEs which can be mitigated are mitigated before a new version is released.
The text was updated successfully, but these errors were encountered: