SOLR-17900 follow-up: narrow four Hadoop-shaded CVE ranges to 9.0.0-9.9.0 - #224
Merged
Conversation
Contributor
Author
|
I accidentally merged the rpevious SOLR-17900 branch... so here is the one I wanted.. |
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.
Follow-up to #216. After digging back into the actual shaded dependency versions, the affected ranges on four of the Hadoop-client CVE statements were too broad.
The four CVEs are attributed to libraries shaded inside
hadoop-client-runtime(in thehdfsmodule). Reading the embeddedpom.propertiesfrom eachhadoop-client-runtime-*.jaracross the Solr 9.x line shows those shaded libs were bumped to fixed versions when Solr moved to Hadoop 3.4.1 in Solr 9.10.0 — one release earlier than the9.10.1bound the statements claimed:So the range on those four moves from
9.0.0-9.10.1to9.0.0-9.9.0, with the body text updated to state the exact fix boundary.The avro entry (CVE-2024-47561 / CVE-2023-39410) keeps its
9.0.0-9.10.1range — avro stayed at 1.9.2 through 9.10.1 and is only fixed in 9.11 (branch_9x, Hadoop 3.4.3 → avro 1.11.4). Its body is updated to make that boundary explicit.All statements remain
not_affected/code_not_reachable; this only tightens the version metadata. Site builds andvexctl mergepasses.