CVE-2022-233059.8CriticalCWE-89

CVE-2022-23305: SQL injection in JDBC Appender in Apache Log4j V1

Apache Software Foundation · Apache Log4j 1.x

Vendor fix available · Affected: Apache Software Foundation Apache Log4j 1.x · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

66.5%probability of exploitation in the next 30 days

99th percentile

050100

Higher than 99% of scored CVEs

9.8CriticalCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

Apache Software Foundation · Apache Log4j 1.x1.2.1; before 2.0-alpha1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: SQL Injection
Vendor: Apache Software Foundation
Published: January 2022
Band: Likely to be exploited (10% or more), January 2022

CoverageNo articles yet

No CyberSIXT article names CVE-2022-23305 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.