CVE-2022-23305

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-01-21. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 67%
CISA-KEV: Not listedEPSS: 67%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
99.2%
KEV
Not listed

Published

January 18, 2022

Last Modified

May 27, 2026

Advisory Details (4)

Auto-updated Jun 20, 2026
No patch confirmed yet.
generic

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

http://www.openwall.com/lists/oss-security/2022/01/18/4

Patch Availability(23)

Vendor / EcosystemFixed in / PatchReleasedSource
redhateap7-xml-security-0:2.2.3-2.redhat_00001.1.el7eap2024-11-25redhat
redhateap7-log4j-jboss-logmanager-0:1.2.2-1.Final_redhat_00002.1.ep7.el72024-08-26redhat
redhatpatch2022-06-30redhat
redhatjbossweb-0:7.5.32-2.Final_redhat_1.2.ep6.el72022-06-30redhat
redhatjbossweb-0:7.5.32-2.Final_redhat_1.2.ep6.el62022-06-30redhat
redhateap7-log4j-0:2.17.1-1.redhat_00001.1.el8eap2022-04-11redhat
redhatlog4j2022-04-11redhat
redhateap7-log4j-0:2.17.1-1.redhat_00001.1.el7eap2022-04-11redhat
redhattomcat-native-0:1.2.23-26.redhat_26.ep7.el72022-02-14redhat
redhatlog4j-eap62022-02-14redhat
redhatsnmp4j-0:3.6.4-0.1.el8ev2022-02-08redhat
redhatpatch2022-02-08redhat
redhatlog4j-0:1.2.17-18.el7_42022-02-07redhat
redhatrh-sso-7/sso74-openshift-rhel8:7.4-452022-02-07redhat
redhatrh-sso-7/sso7-rhel8-operator-bundle:7.5.1-92022-02-07redhat
redhatrh-sso-7/sso74-openj9-openshift-rhel8:7.4-602022-02-07redhat
redhatrh-sso7-keycloak-0:15.0.4-1.redhat_00003.1.el8sso2022-02-07redhat
redhatrh-sso7-keycloak-0:15.0.4-1.redhat_00003.1.el7sso2022-02-07redhat
redhatrh-maven36-log4j12-0:1.2.17-23.4.el72022-02-03redhat
redhateap7-log4j-jboss-logmanager-0:1.2.2-1.Final_redhat_00002.1.el7eap2022-02-03redhat
redhatlog4j-jboss-logmanager-0:1.1.4-3.Final_redhat_00002.1.ep6.el72022-02-03redhat
mavenlog4j:log4jghsa
mavenorg.zenframework.z8.dependencies.commons:log4j-1.2.17ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
log4j:log4j1.1.3 ... 1.2.9 (14 versions)
org.zenframework.z8.dependencies.commons:log4j-1.2.172.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(15)

Data Freshness Timeline

(refreshed 3× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:25 UTCEPSS rescore
  2. 2026-07-09 19:07 UTCEPSS rescore
  3. 2026-07-06 02:21 UTCEPSS rescore
  4. 2026-07-04 06:29 UTCEPSS rescore
  5. 2026-07-04 06:29 UTCEPSS rescore
  6. 2026-07-01 15:04 UTCEPSS rescore
  7. 2026-06-30 23:20 UTCEPSS rescore
  8. 2026-06-30 23:20 UTCEPSS rescore
  9. 2026-06-29 23:04 UTCOSV refresh
  10. 2026-06-29 14:04 UTCEPSS rescore
  11. 2026-06-29 14:04 UTCEPSS rescore
  12. 2026-06-27 03:07 UTCEPSS rescore
  13. 2026-06-25 13:48 UTCEPSS rescore
  14. 2026-06-24 14:03 UTCEPSS rescore
  15. 2026-06-24 14:03 UTCEPSS rescore
  16. 2026-06-23 21:31 UTCEPSS rescore
  17. 2026-06-23 21:31 UTCEPSS rescore
  18. 2026-06-19 19:24 UTCEPSS rescore
  19. 2026-06-19 19:24 UTCEPSS rescore
  20. 2026-06-17 17:51 UTCEPSS rescore
  21. 2026-06-17 17:51 UTCEPSS rescore
  22. 2026-06-16 17:51 UTCEPSS rescore
  23. 2026-06-15 17:46 UTCEPSS rescore
  24. 2026-06-14 23:15 UTCEPSS rescore
  25. 2026-06-14 23:15 UTCEPSS rescore
Show 39 more
  1. 2026-06-13 22:58 UTCEPSS rescore
  2. 2026-06-13 22:58 UTCEPSS rescore
  3. 2026-06-12 23:10 UTCEPSS rescore
  4. 2026-06-12 23:10 UTCEPSS rescore
  5. 2026-06-12 11:40 UTCOSV refresh
  6. 2026-06-11 13:58 UTCEPSS rescore
  7. 2026-06-11 13:58 UTCEPSS rescore
  8. 2026-06-10 22:16 UTCEPSS rescore
  9. 2026-06-10 13:20 UTCEPSS rescore
  10. 2026-06-08 14:15 UTCEPSS rescore
  11. 2026-06-08 14:15 UTCEPSS rescore
  12. 2026-06-07 15:23 UTCEPSS rescore
  13. 2026-06-07 15:23 UTCEPSS rescore
  14. 2026-06-06 13:46 UTCEPSS rescore
  15. 2026-06-06 13:46 UTCEPSS rescore
  16. 2026-06-05 22:45 UTCEPSS rescore
  17. 2026-06-05 06:09 UTCEPSS rescore
  18. 2026-06-05 06:09 UTCEPSS rescore
  19. 2026-06-04 13:11 UTCEPSS rescore
  20. 2026-06-04 13:11 UTCEPSS rescore
  21. 2026-06-02 20:11 UTCEPSS rescore
  22. 2026-06-02 20:11 UTCEPSS rescore
  23. 2026-06-02 20:11 UTCEPSS rescore
  24. 2026-05-31 22:29 UTCEPSS rescore
  25. 2026-05-31 22:29 UTCEPSS rescore
  26. 2026-05-31 00:15 UTCEPSS rescore
  27. 2026-05-31 00:15 UTCEPSS rescore
  28. 2026-05-29 13:42 UTCEPSS rescore
  29. 2026-05-28 13:43 UTCEPSS rescore
  30. 2026-05-28 13:43 UTCEPSS rescore
  31. 2026-05-28 13:43 UTCEPSS rescore
  32. 2026-05-27 13:39 UTCEPSS rescore
  33. 2026-05-27 13:39 UTCEPSS rescore
  34. 2026-05-26 13:43 UTCEPSS rescore
  35. 2026-05-26 07:17 UTCEPSS rescore
  36. 2026-05-26 07:17 UTCEPSS rescore
  37. 2026-05-26 04:39 UTCEG score recompute
  38. 2026-05-26 04:39 UTCVendor advisory
  39. 2026-05-26 04:39 UTCGHSA enrichment

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCAlphabugX/CVE-2022-RCE
    First seen Jan 21, 2022

    test 反向辣鸡数据投放 CVE-2022-23305 工具 利用 教程 Exploit POC

    Open source ↗
  • GitHub PoCHynekPetrak/log4shell-finder
    First seen Dec 14, 2021

    Fastest filesystem scanner for log4shell (CVE-2021-44228, CVE-2021-45046) and other vulnerable (CVE-2017-5645, CVE-2019-17571, CVE-2022-23305, CVE-2022-23307 ... ) instances of log4j library. Excellent performance and low memory footprint.

    Open source ↗

Frequently asked(5)

What is CVE-2022-23305?
CVE-2022-23305 is a critical vulnerability published on January 18, 2022. 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…
When was CVE-2022-23305 disclosed?
CVE-2022-23305 was first published in the National Vulnerability Database on January 18, 2022, with the most recent update on May 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-23305 actively exploited?
CVE-2022-23305 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-23305?
CVE-2022-23305 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-23305?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-23305, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-23305

Explore →

Is Your Infrastructure Affected by CVE-2022-23305?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.