fix(sec): upgrade org.eclipse.jetty:jetty-server to 12.0.0.beta0 - #1279
Open
chncaption wants to merge 1 commit into
Open
fix(sec): upgrade org.eclipse.jetty:jetty-server to 12.0.0.beta0#1279chncaption wants to merge 1 commit into
chncaption wants to merge 1 commit into
Conversation
|
It is not necessary to go all the way to 12.0.0.beta0. This issue has been addressed in versions 9.4.51, 10.0.14, 11.0.14, and 12.0.0.beta0. https://security.snyk.io/vuln/SNYK-SLES155-JETTYSERVER-5721531 |
|
Is this something that will go through? |
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
3 participants
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 happened？
There are 1 security vulnerabilities found in org.eclipse.jetty:jetty-server 9.4.48.v20220622
What did I do？
Upgrade org.eclipse.jetty:jetty-server from 9.4.48.v20220622 to 12.0.0.beta0 for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
The specification of the pull request
PR Specification from OSCS