-
Notifications
You must be signed in to change notification settings - Fork 102
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
Fix CVE-2022-41721 and CVE-2022-27664 #387
Conversation
@luksan47, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
@luksan47, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
@luksan47, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
@luksan47, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
These CVEs come from the prometheus package through a vulnerable version of `golang.org/x/net`. These versions are gone after updating prometheus by running: ``` go get -u github.com/prometheus/common ``` Signed-off-by: Norbert Luksa <[email protected]>
These CVEs come from the prometheus package through a vulnerable version of `golang.org/x/net`. These versions are gone after updating prometheus by running: ``` go get -u github.com/prometheus/common ``` Signed-off-by: Norbert Luksa <[email protected]>
These CVEs come from the prometheus package through a vulnerable version of
golang.org/x/net
.These versions are gone after updating prometheus by running: