[
https://issues.apache.org/jira/browse/RANGER-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912021#comment-17912021
]
Bhavik Patel commented on RANGER-4038:
--------------------------------------
I agree it's tightly coupled, so we won't be able to segregate.
I have reviewed the Jakarta EE migration approach in detail and it seems quick
and clean.
# I have reviewed your PR changes thoroughly and it seems like multiple
changes are missing. Can you double-check once more?
# Can you please mention which functionalities you have validated (Ranger
Admin, Ranger Usersync, Ranger Tagsync, Ranger KMS, Plugins validation)?
Accordingly, I will help you test and try to fill in the gaps.
# We can create a separate branch for Spring Migration once
https://issues.apache.org/jira/browse/RANGER-5017 gets merged into the main
branch, and then we will create a new branch for Spring.
# It seems like Spring 6.0.x and 6.1.x are also vulnerable, so it might be
better to directly migrate to 6.2.x.
> Upgrade spring framework and spring security versions
> -----------------------------------------------------
>
> Key: RANGER-4038
> URL: https://issues.apache.org/jira/browse/RANGER-4038
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Reporter: Himanshu Maurya
> Priority: Major
>
> Pivotal Spring Framework up to (excluding) 6.0.0 suffers from a potential
> remote code execution (RCE) issue if used for Java deserialization of
> untrusted data. Depending on how the library is implemented within a product,
> this issue may or not occur, and authentication may be required.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
