CVE-2022-23305 – org.zenframework.z8.dependencies.commons:log4j-1.2.17

Package

Manager: maven
Name: org.zenframework.z8.dependencies.commons:log4j-1.2.17
Vulnerable Version: >=0 <=2.0

Severity

Level: Critical

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

EPSS: 0.14136 pctl0.94125

Details

SQL Injection in Log4j 1.2.x 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.

Metadata

Created: 2022-01-21T23:26:47Z
Modified: 2022-02-24T12:05:54Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/01/GHSA-65fg-84f6-3jq3/GHSA-65fg-84f6-3jq3.json
CWE IDs: ["CWE-89"]
Alternative ID: GHSA-65fg-84f6-3jq3
Finding: F297
Auto approve: 1