Remediate Log4Shell exposure by upgrading Log4j to 2.17.2#51
Draft
pagarwal-dev with Copilot wants to merge 2 commits into
Draft
Remediate Log4Shell exposure by upgrading Log4j to 2.17.2#51pagarwal-dev with Copilot wants to merge 2 commits into
pagarwal-dev with Copilot wants to merge 2 commits into
Conversation
Copilot
AI
changed the title
[WIP] Fix remote code injection vulnerability in Log4j
Remediate Log4Shell exposure by upgrading Log4j to 2.17.2
Jun 30, 2026
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.
This repository was still pinning Log4j 2.14.1, which is vulnerable to CVE-2021-44228-class issues in the Log4j 2.x line. This change upgrades the logging stack to a patched version and aligns Log4j modules on one fixed release.
Dependency remediation
log4jVersionconstant inbuild.gradle.kts.org.apache.logging.log4j:log4j-core→2.17.2org.apache.logging.log4j:log4j-api→2.17.2Version alignment
JNDI lookup surface check
${jndi...},JndiLookup,jndi:) is present in repository logging code/configuration.dependencies { val log4jVersion = "2.17.2" implementation("org.apache.logging.log4j:log4j-core:$log4jVersion") implementation("org.apache.logging.log4j:log4j-api:$log4jVersion") }