GEODE-10580: Remediate CVE-2026-34478 - Improper Output Neutralization for Logs (support/1.15)#8006
Open
JinwooHwang wants to merge 1 commit intoapache:support/1.15from
Open
GEODE-10580: Remediate CVE-2026-34478 - Improper Output Neutralization for Logs (support/1.15)#8006JinwooHwang wants to merge 1 commit intoapache:support/1.15from
JinwooHwang wants to merge 1 commit intoapache:support/1.15from
Conversation
…n for Logs Upgrade Apache Log4j from 2.25.3 to 2.25.4 on support/1.15 to remediate CVE-2026-34478 (CVSS 6.9 MEDIUM). Also corrects stale Log4j version references (2.17.2, 2.12.0, 2.5) missed during the prior GEODE-10544 upgrade. VULNERABILITY: Log4j Core's Rfc5424Layout (versions 2.21.0 through 2.25.3) is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes (CWE-117, CWE-684). Two issues affect users of stream-based syslog services: - The newLineEscape attribute was silently renamed, disabling newline escaping for TCP framing (RFC 6587) and exposing CRLF injection. - The useTlsMessageFormat attribute was silently renamed, silently downgrading TLS framing (RFC 5425) to unframed TCP without newline escaping. REMEDIATION: Updated all Log4j dependency references to 2.25.4 across dependency constraints, build files, expected POM, resource files, and documentation. Corrected stale 2.17.2/2.12.0/2.5 references that were missed by the prior GEODE-10544 upgrade. References: https://nvd.nist.gov/vuln/detail/CVE-2026-34478 apache/logging-log4j2#4074 https://logging.apache.org/security.html#CVE-2026-34478
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.
Summary
Backport Log4j upgrade from 2.25.3 to 2.25.4 on the
support/1.15branch to remediate CVE-2026-34478. Also corrects stale Log4j version references (2.17.2,2.12.0,2.5) in resource files and documentation that were missed during the prior GEODE-10544 upgrade.Security Vulnerability
Description
Log4j Core's
Rfc5424Layout(versions 2.21.0 through 2.25.3) is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes. Two distinct issues affect users of stream-based syslog services who configureRfc5424Layoutdirectly:newLineEscapeattribute silently renamed — Newline escaping stopped working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output.useTlsMessageFormatattribute silently renamed — Users of TLS framing (RFC 5425) were silently downgraded to unframed TCP (RFC 6587) without newline escaping.Changes
Version string updates across 10 files (34 insertions, 34 deletions):
build-tools/geode-dependency-management/.../DependencyConstraints.groovygeode-assembly/.../management/build.gradlelog4j-slf4j-impldependencyboms/geode-all-bom/.../expected-pom.xml<version>entries in expected POMgeode-assembly/.../assembly_content.txtgeode-assembly/.../gfsh_dependency_classpath.txtgeode-server-all/.../dependency_classpath.txtgeode-docs/.../configuring_log4j2.html.md.erbgeode-docs/.../how_logging_works.html.md.erbgeode-docs/.../weblogic_setting_up_the_module.html.md.erbNote: The prior GEODE-10544 upgrade (2.17.2 → 2.25.3) on
support/1.15only updatedDependencyConstraints.groovy,geode-log4j/build.gradle, and 20 Java test import files. It missed the resource files, expected POM, documentation, and management build.gradle — all of which still referenced older versions. This PR corrects all of them to 2.25.4.No code logic changes — this is a dependency version bump only.
References
Rfc5424Layoutattributes logging-log4j2#4074For all changes, please confirm:
develop)?gradlew buildrun cleanly?