SQL Injection in Log4j 1.2.x

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2022-23305: 66.54% estimated exploitation activity in the next 30 days; percentile 99.29 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

21 Jan 2022, 23:26 UTC

Last modified by the source

8 Jun 2026, 23:39 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-65fg-84f6-3jq3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-23305

Advisory: SQL Injection in Log4j 1.2.x
IDs: CVE-2022-23305, GHSA-65fg-84f6-3jq3
Record: https://patchnext.com/advisories/cve-2022-23305 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.zenframework.z8.dependencies.commons:log4j-1.2.17: affected <= 2.0
- Maven log4j:log4j: affected <= 1.2.17

## Suggested inspection (read-only)
- Maven org.zenframework.z8.dependencies.commons:log4j-1.2.17: check the installed version with your package manager.
- Maven log4j:log4j: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.zenframework.z8.dependencies.commons:log4j-1.2.17, log4j:log4j.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-65fg-84f6-3jq3 (GitHub-reviewed advisory GHSA-65fg-84f6-3jq3 lists affected ranges: Maven log4j:log4j >=0 =0 <=2.0)

Commands are suggestions: review each one before running it.