Issue 5: Update log4j and mitigate CVEs.#8
Issue 5: Update log4j and mitigate CVEs.#8jameswsullivan wants to merge 1 commit intoDSpace:mainfrom
Conversation
Handle Resolver Plugin InstallationThe installation process remains largely the same besides the following changes: In step 6, instead of using create a In step 8, instead of using: in Add log4j2 artifacts to handle softwareDownload the latest handle software from https://www.handle.net/download_hnr.html , follow the normal installation process detailed here, and add the following log4j artifacts into the handle software's Or, use my unofficial copy of the handle software with the updates already added. |
Handle Software VulnerabilitiesIf you opt to use my updated version of the handle software, it also contains jetty updates that mitigate the following CVEs:
|
|
@kshepherd @misilot @tdonohue Alright the PR is up. |
|
@jameswsullivan thank you for your wok on this, it's highly appreciated. |
As in my reply here , this PR resolves the following CVEs:
log4j 1.2.17 -> 2.25.3:
The fix updates
log4j 1.2.17with:log4j-api 2.25.3log4j-core 2.25.3log4j-1.2-api 2.25.3log4j-1.2-apiprovides the compatibility bridge so no code change is needed.commons-lang 2.6 -> 3.20.0:
Other changes:
While working on the vulns I also changed the maven plugin to 3.11.0 and use Java 21 for build, as I was getting these errors:
Minor changes to the wiki are also needed to use the new log4j2 with the handle software, which I'll detail in a reply under this PR.