-
Notifications
You must be signed in to change notification settings - Fork 78
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
OCPBUGS-33146: [release-4.14] OCPBUGS-16483: Update apimachinery dependency to remove goproxy dep #709
OCPBUGS-33146: [release-4.14] OCPBUGS-16483: Update apimachinery dependency to remove goproxy dep #709
Conversation
A denial of service (DoS) via unspecified vectors issue was found in goproxy (CVE-2023-37788). goproxy is not used directly by the agent. It is pulled in by apimachinery. apimachinery ceases to use goproxy after v0.27.0. To prevent the potential issue, apimachiney is updated to v0.27.2.
@rwsu: This pull request references Jira Issue OCPBUGS-16483, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
/jira cherrypick OCPBUGS-16483 |
@rwsu: Jira Issue OCPBUGS-16483 has been cloned as Jira Issue OCPBUGS-33146. Will retitle bug to link to clone. 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 openshift-eng/jira-lifecycle-plugin repository. |
@rwsu: This pull request references Jira Issue OCPBUGS-33146, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
/jira refresh |
@rwsu: This pull request references Jira Issue OCPBUGS-33146, which is valid. 7 validation(s) were run on this bug
Requesting review from QA contact: 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 openshift-eng/jira-lifecycle-plugin repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gamli75, rwsu 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 |
@rwsu: all tests passed! 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-sigs/prow repository. I understand the commands that are listed here. |
4106eb4
into
openshift:release-4.14
@rwsu: Jira Issue OCPBUGS-33146: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-33146 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 openshift-eng/jira-lifecycle-plugin repository. |
[ART PR BUILD NOTIFIER] Distgit: ose-agent-installer-node-agent |
This is a manual cherrypick of PR#590
A denial of service (DoS) via unspecified vectors issue was found in goproxy (CVE-2023-37788). goproxy is not used directly by the agent. It is pulled in by apimachinery. apimachinery ceases to use goproxy after v0.27.0.
To prevent the potential issue, apimachiney is updated to v0.27.2.