Skip to main content
Public proof of conceptFix available

CVE-2022-23305

A public proof of concept exists; no exploitation attested.

  • Published2022-01-18
  • WeaknessCWE-89

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2022-01-1816:15CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub
  3. 2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-23305?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-23305?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Oracle business intelligence
BranchAffectedFixed in
5.9= 5.9.0.0.0no fix published
12.2= 12.2.1.3.0no fix published
12.2= 12.2.1.4.0no fix published
Oracle financial services revenue management and billing analytics
BranchAffectedFixed in
2.7= 2.7.0.0no fix published
2.7= 2.7.0.1no fix published
2.8= 2.8.0.0no fix published
Oracle weblogic server
BranchAffectedFixed in
12.2= 12.2.1.3.0no fix published
12.2= 12.2.1.4.0no fix published
14.1= 14.1.1.0.0no fix published

25 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

Detection

read 2026-10-23 19:23 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
4 repositories, unverifiedHynekPetrak/log4shell-finderAlphabugX/CVE-2022-RCEtkomlodi/CVE-2022-23305_POChoor113/CVE-2022-23305-Demo-and-Whitebox-Report
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2026-05-22
  • OpenCVESSVC decisionnone—
  • CISA-ADPCVSS 3.19.82026-05-22
  • NVDCVSS 3.19.8read 2026-10-23
  • NVDCVSS 2.06.8read 2026-10-23
  • CNAweakness (CWE)CWE-89read 2026-10-23
  • NVDweakness (CWE)CWE-89read 2026-10-23
  • FIRST EPSSEPSS score66.5 %read 2026-10-23
  • PoC-in-GitHubproof of concept4read 2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2022-01-18
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2022-23305?

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.

Is CVE-2022-23305 actively exploited?

Active exploitation of CVE-2022-23305 has not been confirmed. Its EPSS score was 66.5% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-23305?

CVE-2022-23305 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database