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
Bug 1924476: handle CVE-2021-3121 #139
Bug 1924476: handle CVE-2021-3121 #139
Conversation
/retitle Bug 1924476: handle CVE-2021-3121 |
@yboaron: This pull request references Bugzilla bug 1924476, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/hold |
go.mod
Outdated
@@ -31,3 +29,5 @@ require ( | |||
k8s.io/klog v0.3.3 // indirect | |||
k8s.io/utils v0.0.0-20190607212802-c55fbcfc754a // indirect | |||
) | |||
|
|||
replace github.com/gogo/protobuf => github.com/gogo/protobuf v1.3.2 |
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.
Can we not just do:
go get github.com/gogo/protobuf
go mod vendor
to update this version?
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.
I copy/paste from cluster-logging-operator fix
I guess we can use your approach
Set protobuf 1.3.2, check [1] [1] https://access.redhat.com/security/cve/CVE-2021-3121
/bugzilla refresh |
@cybertron: This pull request references Bugzilla bug 1924476, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (vvoronko@redhat.com), skipping review request. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest |
/lgtm The ipv6 job passed, and the ipv4 one failed on something unrelated. I think you can remove the hold and merge this. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cybertron, yboaron The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel We're coming up on code freeze, let's get this in. |
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@yboaron: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@yboaron: All pull requests linked via external trackers have merged: Bugzilla bug 1924476 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Set protobuf 1.3.2, check [1]
[1]
https://access.redhat.com/security/cve/CVE-2021-3121