CVE-2022-23305 (Critical) detected in log4j-1.2.17.jar
mend-bolt-for-github opened this issue · comments
CVE-2022-23305 - Critical Severity Vulnerability
Vulnerable Library - log4j-1.2.17.jar
Apache Log4j 1.2
Path to dependency file: /owner-extras/pom.xml
Path to vulnerable library: /owner-extras/pom.xml
Dependency Hierarchy:
- curator-framework-4.3.0.jar (Root Library)
- curator-client-4.3.0.jar
- zookeeper-3.5.7.jar
- ❌ log4j-1.2.17.jar (Vulnerable Library)
- zookeeper-3.5.7.jar
- curator-client-4.3.0.jar
Found in HEAD commit: 12e21721ff1098fe44de120bf2737fd994f40fa6
Found in base branch: master
Vulnerability Details
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
Publish Date: 2022-01-18
URL: CVE-2022-23305
CVSS 3 Score Details (9.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Origin: https://reload4j.qos.ch/
Release Date: 2022-01-18
Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.2
Step up your Open Source Security Game with Mend here