OCPBUGS-25513: CVE-2023-48795 Update crypto lib

[jaypoulz]

/kind Bug

[openshift-ci-robot]

@jaypoulz: This pull request references Jira Issue OCPBUGS-25513, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @djslavens

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

/kind Bug

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.

[jaypoulz]

/assign @yussufsh

[openshift-ci]

@jaypoulz: 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/test-infra repository. I understand the commands that are listed here.

[djslavens]

/lgtm

[yussufsh]

@jaypoulz is there a way you could auto assign those cve bugs to me by default?
The thing is these deps updates are fixed upstream regularly, we just need to periodically rebase the changes.
Thinking we should automate the process of merging upstream or keep a look at cve issues and update manually when needed. If you have any alternate approach which other projects are using then let me know.

[jaypoulz]

@yussufsh I can do that, the only caveat will be that CVEs of high severity and above will have embargoed status, so they'll probably not be visible to you. But for general CVEs I'm more than happy to route them to you so you can just arrange an upstream sync. :)

[yussufsh]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: djslavens, jaypoulz, yussufsh

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:

• OWNERS [yussufsh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@jaypoulz: Jira Issue OCPBUGS-25513: All pull requests linked via external trackers have merged:

• openshift/ibm-powervs-block-csi-driver#73

Jira Issue OCPBUGS-25513 has been moved to the MODIFIED state.

In response to this:

/kind Bug

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.

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-powervs-block-csi-driver-container-v4.16.0-202401230706.p0.g972a508.assembly.stream for distgit ose-powervs-block-csi-driver.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.16.0-0.nightly-2024-01-24-031529