We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to Jfrog Xray scanner detected the following vulnerabilities, is it possible to create new release to resolve them?
||Severity || ID || Component ||Fix Version || | critical | CVE-2024-24790 | github.com/golang/go:1.21.5 | 1.21.11, 1.22.4 | | critical | CVE-2023-49569 | github.com/go-git/go-git/v5:5.2.0 | 5.11.0 | |High| CVE-2022-21698 | github.com/prometheus/client_golang:1.1.0 | 1.11.1| |High| CVE-2023-39325 | golang.org/x/net:0.0.0-20201224014010-6772e930b67b | 0.17.0| |High| CVE-2022-41723 | golang.org/x/net:0.0.0-20201224014010-6772e930b67b | 0.7.0| |High| CVE-2021-43565 | golang.org/x/crypto:0.0.0-20200622213623-75b288015ac9 | 0.0.0-20211202192323-5770296d904e | |High| CVE-2021-33194 | golang.org/x/net:0.0.0-20201224014010-6772e930b67b| 0.0.0-20210520170846-37e1c6afe023 | |High| CVE-2022-27191 | golang.org/x/crypto:0.0.0-20200622213623-75b288015ac9 |0.0.0-20220314234659-1baeb1ce4c0b| |High| CVE-2022-27664 | golang.org/x/net:0.0.0-20201224014010-6772e930b67b |0.0.0-20220906165146-f3363e06e74c| |High| CVE-2020-29652 | golang.org/x/crypto:0.0.0-20200622213623-75b288015ac9 |0.0.0-20201216223049-8b5274cf687f | |High| CVE-2023-49568 | github.com/go-git/go-git/v5:5.2.0 | 5.11.0 | |High| CVE-2023-44487 | golang.org/x/net:0.0.0-20201224014010-6772e930b67b |0.17.0|
The text was updated successfully, but these errors were encountered:
Meanwhile, there is a bug ticket in Jira referencing this issue: https://jira.atlassian.com/browse/OPSGENIE-2319
Sorry, something went wrong.
No branches or pull requests
According to Jfrog Xray scanner detected the following vulnerabilities, is it possible to create new release to resolve them?
The text was updated successfully, but these errors were encountered: