[WIP]HIVE-29299: Upgrade Spring to 6.2.12 and spring-ldap-core to 3.3.4 to resolve CVE-2025-41249#6401
Draft
hemanthumashankar0511 wants to merge 1 commit intoapache:masterfrom
Draft
Conversation
|
hemanthumashankar0511
changed the title
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
2 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 changes were proposed in this pull request?
This PR upgrades two Spring-related dependencies to address a known security vulnerability:
spring.version: 5.3.39 → 6.2.12 (in both pom.xml and standalone-metastore/pom.xml)
spring-ldap-core: 2.4.4 → 3.3.4 (in both pom.xml and standalone-metastore/pom.xml)
Why are the changes needed?
This upgrade addresses CVE-2025-41249, which affects spring-core versions through 5.3.39. The previously used spring-ldap-core:2.4.4 transitively pulled in the vulnerable spring-core:5.3.39. Upgrading to spring-ldap-core:3.3.4 brings in a Spring 6.2.12 baseline, fully resolving the vulnerability.
The fix has been verified across both the standalone-metastore and ql modules, neither module's dependency tree contains spring-core:5.3.x after this change.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Dependency tree verification : Confirmed via mvn dependency:tree on both the standalone-metastore and ql modules that spring-core:5.3.39 is fully replaced by 6.2.12 with no residual vulnerable transitive references.