Update photon 4.0 image to resolve CVEs#539
Open
deepakkinni wants to merge 1 commit intovmware-tanzu:mainfrom
Open
Update photon 4.0 image to resolve CVEs#539deepakkinni wants to merge 1 commit intovmware-tanzu:mainfrom
deepakkinni wants to merge 1 commit intovmware-tanzu:mainfrom
Conversation
Signed-off-by: Deepak Kinni <dkinni@vmware.com>
|
Sorry, some of the pre-check tests are failing for this PR ! Please check the Jenkins job for more details |
Collaborator
|
@deepakkinni Overall change looks good to me. In the scan result, I still see some Medium/Low CVEs. Do we need to fix them or not? |
Collaborator
Author
These are existing CVEs, since they are LOW and MEDIUM it's not essential to fix them. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Resolve CVE-2023-2603
Which issue(s) this PR fixes:
Fixes #
Testing:
Scan Results:
Does this PR introduce a user-facing change?: