CVE-2022-23302
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.
Deserialization of untrusted data in JMSSink in Apache Log4j 1.x
rank 50 = 16 + 22 + 0 + 12 + 0
rank@v1 · this cycle
Someone is already using it
CISA KEV catalog · public proof-of-concept · FIRST EPSS
EPSS 0.63556 · without this subject the record ranks 34
What it costs you if it fires
NVD CVSS base score, then the CNA's own
CVSS 8.8, from NVD · without this subject the record ranks 28
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 50
How much of the world it touches
NVD CPE configurations
37 products in the CPE ranges · without this subject the record ranks 38
Someone else already set the date
CISA KEV remediation due date
no CISA due date · without this subject the record ranks 50
Hindsight · the state
Foresight · where to check next
log4j 1.x is one instance of CWE-502, deserialization of untrusted data. The index holds 3513 prior instances of this class, 76 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 (free with an account: one stack of three products)
Record your call
Keep your verdict, your reason and the evidence together. The record takes its date when you save it.
Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.
Choose 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.
Show full BOD 26-04 deadline
CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table
Exploit Status & Known PoCs a ladder, not a score
Current rung: Nothing observed in held sources.
- RUNG 1Nothing observed in held sources
- RUNG 2Proof-of-concept published
- RUNG 3Exploited in the wild · CISA KEV listed
- RUNG 4Ransomware campaign use known
Affected & Fixed Versions as published
Show all 37 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.
$3.17M = $4.99M incident cost x 1 exposure x 0.63556 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.
What it is stated by the CNA
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. 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. receipt
NVD's analysis a second authority
- severity
- 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- weakness
- CWE-502
- affected versions
- apache log4j >= 1.0.1 <= 1.2.17; qos reload4j < 1.2.18.1; oracle advanced supply chain planning 12.1; and 34 more, listed in full below
- also scored by
- 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
check it yourself lists.apache.org logging.apache.org openwall.com oracle.com security.netapp.com oracle.com receipt
Dated events
Movement the material steps
Show all 50 observations
50 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 full biography
The record had been public for 4 years, 6 months when this index was last written.
The pattern, elsewhere
log4j 1.x is one instance of CWE-502, deserialization of untrusted data. The index holds 3513 prior instances of this class, 76 KEV-listed. 5 neighbors share the mechanism; each carries its own record state. cwe-consequences@4.20
3513 records in this class held. The six above are ranked by exploit maturity, then recency.
Siblings and hubs
Records related to this one
Its defect family
apache software foundation apache log4j
Of the 5 records in this family, this is the only one holding a stated fix version: 2.0-alpha1.
Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.
Family membership: computed, pro@dim2000
This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.
Browse the index from here
These are index-wide views, not findings about CVE-2022-23302.
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.