Skip to content
Noroxi
NVD / CVE Program· CNA apache

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

CriticalCVSS 9.8 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: Plan (action score 59/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 66.5% (FIRST EPSS); higher than 99.2% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: parfait (AlmaLinux:8) 0.5.4-4.module_el8.5.0+235+62ea7738, 0.5.4-4.module_el8.5.0+2610+de2b8c0b; parfait-examples (AlmaLinux:8) 0.5.4-4.module_el8.5.0+2610+de2b8c0b, 0.5.4-4.module_el8.5.0+235+62ea7738; parfait-javadoc (AlmaLinux:8) 0.5.4-4.module_el8.5.0+2610+de2b8c0b, 0.5.4-4.module_el8.5.0+235+62ea7738.
  • Mentioned 4 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to parfait (AlmaLinux:8) 0.5.4-4.module_el8.5.0+235+62ea7738, 0.5.4-4.module_el8.5.0+2610+de2b8c0b; parfait-examples (AlmaLinux:8) 0.5.4-4.module_el8.5.0+2610+de2b8c0b, 0.5.4-4.module_el8.5.0+235+62ea7738; parfait-javadoc (AlmaLinux:8) 0.5.4-4.module_el8.5.0+2610+de2b8c0b, 0.5.4-4.module_el8.5.0+235+62ea7738 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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
Jan 18, 2022
Updated
Jun 17, 2026
EPSS
66.5% · 99th percentile

Report tools

JSON

Action score

59

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
20 / 30 · 66.5%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-23305

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
apachelog4j
netappsnapmanager
broadcombrocade sannav
qosreload4j
oracleadvanced supply chain planning
oraclebusiness intelligence
oraclebusiness process management suite
oraclecommunications eagle ftp table base retrieval
oraclecommunications instant messaging server
oraclecommunications messaging server
oraclecommunications network integrity
oraclecommunications offline mediation controller

and 16 more

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • Apache Software Foundation Apache Log4j 1.x

    • 1.2.1 and later · before unspecifiedaffected
    • unspecified and later · before 2.0-alpha1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8parfaitbefore 0.5.4-4.module_el8.5.0+235+62ea77380.5.4-4.module_el8.5.0+235+62ea7738
AlmaLinux:8parfaitbefore 0.5.4-4.module_el8.5.0+2610+de2b8c0b0.5.4-4.module_el8.5.0+2610+de2b8c0b
AlmaLinux:8parfait-examplesbefore 0.5.4-4.module_el8.5.0+2610+de2b8c0b0.5.4-4.module_el8.5.0+2610+de2b8c0b
AlmaLinux:8parfait-examplesbefore 0.5.4-4.module_el8.5.0+235+62ea77380.5.4-4.module_el8.5.0+235+62ea7738
AlmaLinux:8parfait-javadocbefore 0.5.4-4.module_el8.5.0+2610+de2b8c0b0.5.4-4.module_el8.5.0+2610+de2b8c0b
AlmaLinux:8parfait-javadocbefore 0.5.4-4.module_el8.5.0+235+62ea77380.5.4-4.module_el8.5.0+235+62ea7738
AlmaLinux:8pcp-parfait-agentbefore 0.5.4-4.module_el8.5.0+235+62ea77380.5.4-4.module_el8.5.0+235+62ea7738
AlmaLinux:8pcp-parfait-agentbefore 0.5.4-4.module_el8.5.0+2610+de2b8c0b0.5.4-4.module_el8.5.0+2610+de2b8c0b
AlmaLinux:8si-unitsbefore 0.6.5-2.module_el8.5.0+235+62ea77380.6.5-2.module_el8.5.0+235+62ea7738
AlmaLinux:8si-unitsbefore 0.6.5-2.module_el8.5.0+2610+de2b8c0b0.6.5-2.module_el8.5.0+2610+de2b8c0b
AlmaLinux:8si-units-javadocbefore 0.6.5-2.module_el8.5.0+2610+de2b8c0b0.6.5-2.module_el8.5.0+2610+de2b8c0b
AlmaLinux:8si-units-javadocbefore 0.6.5-2.module_el8.5.0+235+62ea77380.6.5-2.module_el8.5.0+235+62ea7738
AlmaLinux:8unit-apibefore 1.0-5.module_el8.5.0+235+62ea77381.0-5.module_el8.5.0+235+62ea7738
AlmaLinux:8unit-apibefore 1.0-5.module_el8.5.0+2610+de2b8c0b1.0-5.module_el8.5.0+2610+de2b8c0b
AlmaLinux:8unit-api-javadocbefore 1.0-5.module_el8.5.0+235+62ea77381.0-5.module_el8.5.0+235+62ea7738
AlmaLinux:8unit-api-javadocbefore 1.0-5.module_el8.5.0+2610+de2b8c0b1.0-5.module_el8.5.0+2610+de2b8c0b
AlmaLinux:8uom-libbefore 1.0.1-6.module_el8.5.0+2610+de2b8c0b1.0.1-6.module_el8.5.0+2610+de2b8c0b
AlmaLinux:8uom-libbefore 1.0.1-6.module_el8.5.0+235+62ea77381.0.1-6.module_el8.5.0+235+62ea7738
AlmaLinux:8uom-lib-javadocbefore 1.0.1-6.module_el8.5.0+2610+de2b8c0b1.0.1-6.module_el8.5.0+2610+de2b8c0b
AlmaLinux:8uom-lib-javadocbefore 1.0.1-6.module_el8.5.0+235+62ea77381.0.1-6.module_el8.5.0+235+62ea7738
AlmaLinux:8uom-parentbefore 1.0.3-3.module_el8.5.0+235+62ea77381.0.3-3.module_el8.5.0+235+62ea7738
AlmaLinux:8uom-parentbefore 1.0.3-3.module_el8.5.0+2610+de2b8c0b1.0.3-3.module_el8.5.0+2610+de2b8c0b
AlmaLinux:8uom-sebefore 1.0.4-3.module_el8.5.0+235+62ea77381.0.4-3.module_el8.5.0+235+62ea7738
AlmaLinux:8uom-sebefore 1.0.4-3.module_el8.5.0+2610+de2b8c0b1.0.4-3.module_el8.5.0+2610+de2b8c0b

+96

Other highest-scoring records for the same primary product.

  • CVE-2021-44228Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpointsKEV
    100Now
  • CVE-2021-45046Apache Log4j2 Thread Context Message Pattern and Context Lookup Pattern vulnerable to a denial of service attackKEV
    96Now
  • CVE-2017-5645In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another…
    66This week

Published before and after this one in the same product

  • ← EarlierCVE-2021-44832Dec 28, 2021 · Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration
    55Plan
  • ← EarlierCVE-2022-23302Jan 18, 2022 · Deserialization of untrusted data in JMSSink in Apache Log4j 1.x
    54Plan
  • Later →CVE-2023-26464Mar 10, 2023 · Apache Log4j 1.x (EOL) allows DoS in Chainsaw and SocketAppender
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:parfait0.5.4-4.module_el8.5.0+235+62ea7738 · AlmaLinux:8Package registry (OSV)
almalinux:parfait-examples0.5.4-4.module_el8.5.0+2610+de2b8c0b · AlmaLinux:8Package registry (OSV)
almalinux:parfait-javadoc0.5.4-4.module_el8.5.0+235+62ea7738 · AlmaLinux:8Package registry (OSV)
almalinux:pcp-parfait-agent0.5.4-4.module_el8.5.0+2610+de2b8c0b · AlmaLinux:8Package registry (OSV)
almalinux:si-units0.6.5-2.module_el8.5.0+235+62ea7738 · AlmaLinux:8Package registry (OSV)
almalinux:si-units-javadoc0.6.5-2.module_el8.5.0+2610+de2b8c0b · AlmaLinux:8Package registry (OSV)
almalinux:unit-api1.0-5.module_el8.5.0+2610+de2b8c0b · AlmaLinux:8Package registry (OSV)
almalinux:unit-api-javadoc1.0-5.module_el8.5.0+2610+de2b8c0b · AlmaLinux:8Package registry (OSV)
almalinux:uom-lib1.0.1-6.module_el8.5.0+2610+de2b8c0b · AlmaLinux:8Package registry (OSV)
almalinux:uom-lib-javadoc1.0.1-6.module_el8.5.0+2610+de2b8c0b · AlmaLinux:8Package registry (OSV)
almalinux:uom-parent1.0.3-3.module_el8.5.0+235+62ea7738 · AlmaLinux:8Package registry (OSV)
almalinux:uom-se1.0.4-3.module_el8.5.0+235+62ea7738 · AlmaLinux:8Package registry (OSV)
debian:apache-log4j1.21.2.17-11 · Debian:12Package registry (OSV)
opensuse:kafka2.1.0-bp153.2.6.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:kafka-kit2.1.0-bp153.2.6.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:log4j1.2.17-5.9.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:log4j121.2.17-4.9.1 · openSUSE:Leap 15.3Package registry (OSV)
red hat:parfait0:0.5.4-4.module+el8.4.0+13998+1b70e2b7 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:parfait-examples0:0.5.4-4.module+el8.4.0+13998+1b70e2b7 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:parfait-javadoc0:0.5.4-4.module+el8.4.0+13998+1b70e2b7 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:pcp-parfait-agent0:0.5.4-4.module+el8.4.0+13998+1b70e2b7 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:si-units0:0.6.5-2.module+el8+2463+615f6896 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:si-units-javadoc0:0.6.5-2.module+el8+2463+615f6896 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:unit-api0:1.0-5.module+el8+2463+615f6896 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:unit-api-javadoc0:1.0-5.module+el8+2463+615f6896 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:uom-lib0:1.0.1-6.module+el8+2463+615f6896 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:uom-lib-javadoc0:1.0.1-6.module+el8+2463+615f6896 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:uom-parent0:1.0.3-3.module+el8+2463+615f6896 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:uom-se0:1.0.4-3.module+el8+2463+615f6896 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
rocky linux:parfait0:0.5.4-4.module+el8.5.0+728+553fbdb8 · Rocky Linux:8Package registry (OSV)

+20

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×4

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHub4 repositories2021-12-14 → 2026-10-17

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-36 d
  2. Published
  3. TodayNov 14, 2026+1761 d

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-primary

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = '" + owner + "'");

Fixed

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = $1",  [owner]);

References

All records