NMS-15663: spring security backport #6393
Merged
Conversation
This file contains 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
RangerRick
changed the title
This reverts commit 76dca7a. Fixes: * CVE-2022-22976: BCrypt skips salt rounds for work factor of 31 * CVE-2022-22978: Authorization Bypass in RegexRequestMatcher
RangerRick
force-pushed
the
jira/NMS-15663-spring-security-backport-smoke
branch
from
e18cb22
to
6f05921
Compare
|
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.
This PR is almost entirely different from how I went about this last time.
The biggest change is that I created new "servicemix" jars with proper OSGi metadata, which made things quite a bit less weird as far as handling startup safely.
I will also make a foundation-2023 version of this before merging, to make sure nothing goes strange moving forward to a newer Karaf.
Fixes:
External References