CVE-2022-23305
No source can show you its own past. This one can.
Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.
SQL injection in JDBC Appender in Apache Log4j V1
rank 60 = 25 + 25 + 0 + 10 + 0
rank@v1 · this cycle
Someone is already using it
CISA KEV catalog · public proof-of-concept · FIRST EPSS
EPSS 0.66537 · without this subject the record ranks 35
What it costs you if it fires
NVD CVSS base score, then the CNA's own
CVSS 9.8, from NVD · without this subject the record ranks 35
It is getting worse, not staying still
FIRST EPSS series, rescorings and bad loads removed
no persisting rise in 365 days · without this subject the record ranks 60
How much of the world it touches
NVD CPE configurations
20 products in the CPE ranges · without this subject the record ranks 50
Someone else already set the date
CISA KEV remediation due date
no CISA due date · without this subject the record ranks 60
$3.32M = $4.99M incident cost x 1 exposure x 0.66537 likelihood
udv@v1 · unaudited · wrong for you until you say what you run
$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.
Hindsight · the state
Foresight · where to check next
log4j 1.x is one instance of CWE-89, improper neutralization of special elements used in an sql command ('sql injection'). The index holds 20889 prior instances of this class, 31 KEV-listed. 5 neighbors share the mechanism; each carries its own record state. taxonomy@v1
Running Apache Log4j 1.x? Check your version
A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.
Watch this record
Matches your own product list against every record this index holds, and tells you when one of them moves.
Set up a watchlist (needs a Practitioner account)
Record your call
Keep your verdict, your reason and the evidence together. The record takes its date when you save it.
AcceptDeferPatch by…Not affectedMitigatedChoose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.
Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.
Harm, if it fires from the vector and the weakness
Written for the ticket you're about to file.
CISA KEV & Federal Remediation Deadline from the record and CISA
The fix, and how long it's been waiting.
Exploit Status & Known PoCs a ladder, not a score
Current rung: Proof-of-concept published · 3 public repositories, 2021-12-14.
- RUNG 1Nothing observed in held sources
- RUNG 2Proof-of-concept published · 3 public repositories2021-12-14receipt
- RUNG 3Exploited in the wild · CISA KEV listed
- RUNG 4Ransomware campaign use known
Affected & Fixed Versions as published
Show all 20 published ranges
A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.
What it is stated by the CNA
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. receipt
Read the rest of the CNA's description
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.
NVD's analysis a second authority
- severity
- 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- weakness
- CWE-89
- affected versions
- apache log4j >= 1.2 <= 1.2.17; qos reload4j < 1.2.18.2; oracle advanced supply chain planning 12.1; and 17 more, listed in full below
- also scored by
- 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
check it yourself logging.apache.org lists.apache.org openwall.com oracle.com security.netapp.com oracle.com receipt
Dated events
Movement the material steps
Show all 60 observations
60 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt
The pattern, elsewhere
log4j 1.x is one instance of CWE-89, improper neutralization of special elements used in an sql command ('sql injection'). The index holds 20889 prior instances of this class, 31 KEV-listed. 5 neighbors share the mechanism; each carries its own record state. [email protected]
20889 records in this class held. The six above are ranked by exploit maturity, then recency.
Siblings and hubs
Records related to this one
None. No alias set, and nothing in the corpus cites this identifier or shares its product family within 60 days.
Browse the index from here
These are index-wide views, not findings about CVE-2022-23305.
What usually comes next
Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.