Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely exe
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
- Published
- Dec 20, 2019
- Updated
- Jun 16, 2026
- EPSS
- 69.1% · 99th percentile
- CWE
- CWE-502
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
60
This week
Don’t wait for the next maintenance window.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 21 / 30 · 69.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| apache | log4j | cpe:2.3:a:apache:log4j |
| apache | bookkeeper | cpe:2.3:a:apache:bookkeeper |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
| netapp | oncommand system manager | cpe:2.3:a:netapp:oncommand_system_manager |
| netapp | oncommand workflow automation | cpe:2.3:a:netapp:oncommand_workflow_automation |
| oracle | application testing suite | cpe:2.3:a:oracle:application_testing_suite |
| oracle | communications network integrity | cpe:2.3:a:oracle:communications_network_integrity |
| oracle | endeca information discovery studio | cpe:2.3:a:oracle:endeca_information_discovery_studio |
| oracle | financial services lending and leasing | cpe:2.3:a:oracle:financial_services_lending_and_leasing |
| oracle | mysql enterprise monitor | cpe:2.3:a:oracle:mysql_enterprise_monitor |
and 5 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache bookkeeperbefore 4.14.3
- apache log4jup to 1.2.17 inclusive
- canonical ubuntu linux18.04
- debian debian linux10.0
- debian debian linux8.0
- debian debian linux9.0
- netapp oncommand system manager3.0 and later · up to 3.1.3 inclusive
- netapp oncommand workflow automationall versions
- opensuse leap15.1
- oracle application testing suite13.3.0.1
- oracle communications network integrity7.3.2 and later · up to 7.3.6 inclusive
- oracle endeca information discovery studio3.2.0
- oracle financial services lending and leasing14.1.0 and later · up to 14.8.0 inclusive
- oracle financial services lending and leasing12.5.0
- oracle mysql enterprise monitorup to 8.0.29 inclusive
- oracle primavera gateway17.12.0 and later · up to 17.12.7 inclusive
- oracle primavera gateway16.2 and later · up to 16.2.11 inclusive
- oracle rapid planning12.1
- oracle rapid planning12.2
- oracle retail extract transform and load19.0
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 Log4j
- versions up to 1.2.17affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | apache-log4j1.2 | before 1.2.17-8+deb10u1 | 1.2.17-8+deb10u1 |
| Debian:12 | apache-log4j1.2 | before 1.2.17-9 | 1.2.17-9 |
| Debian:8 | apache-log4j1.2 | before 1.2.17-5+deb8u1 | 1.2.17-5+deb8u1 |
| Debian:9 | apache-log4j1.2 | before 1.2.17-7+deb9u1 | 1.2.17-7+deb9u1 |
| Maven | log4j:log4j | from 1.2 · up to and including 1.2.17 | — |
| Maven | org.zenframework.z8.dependencies.commons:log4j-1.2.17 | all versions | — |
| openSUSE:Leap 15.1 | log4j | before 1.2.17-lp151.5.3.1 | 1.2.17-lp151.5.3.1 |
| openSUSE:Leap 15.1 | log4j-mini | before 1.2.17-lp151.5.3.1 | 1.2.17-lp151.5.3.1 |
| Red Hat:enterprise_linux:7::client | log4j | before 0:1.2.17-16.el7_4 | 0:1.2.17-16.el7_4 |
| Red Hat:enterprise_linux:7::client | log4j-javadoc | before 0:1.2.17-16.el7_4 | 0:1.2.17-16.el7_4 |
| Red Hat:enterprise_linux:7::client | log4j-manual | before 0:1.2.17-16.el7_4 | 0:1.2.17-16.el7_4 |
| Red Hat:jboss_enterprise_application_platform:5::el5 | log4j | before 0:1.2.14-19.patch_01.ep5.el5 | 0:1.2.14-19.patch_01.ep5.el5 |
| Red Hat:jboss_enterprise_application_platform:5::el6 | log4j | before 0:1.2.14-19.patch_01.ep5.el6 | 0:1.2.14-19.patch_01.ep5.el6 |
| Red Hat:jboss_enterprise_application_platform:6::el6 | jboss-ec2-eap | before 0:7.5.17-1.Final_redhat_4.ep6.el6 | 0:7.5.17-1.Final_redhat_4.ep6.el6 |
| Red Hat:jboss_enterprise_application_platform:6::el6 | jboss-ec2-eap-samples | before 0:7.5.17-1.Final_redhat_4.ep6.el6 | 0:7.5.17-1.Final_redhat_4.ep6.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-jboss-ec2-eap | before 0:7.0.8-1.GA_redhat_1.ep7.el6 | 0:7.0.8-1.GA_redhat_1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-jboss-ec2-eap-samples | before 0:7.0.8-1.GA_redhat_1.ep7.el6 | 0:7.0.8-1.GA_redhat_1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el7 | eap7-jboss-ec2-eap | before 0:7.0.8-1.GA_redhat_1.ep7.el7 | 0:7.0.8-1.GA_redhat_1.ep7.el7 |
| Red Hat:jboss_enterprise_application_platform:7::el7 | eap7-jboss-ec2-eap-samples | before 0:7.0.8-1.GA_redhat_1.ep7.el7 | 0:7.0.8-1.GA_redhat_1.ep7.el7 |
| Red Hat:jboss_enterprise_web_server:3.1::el6 | log4j-eap6 | before 0:1.2.16-12.redhat_3.1.ep6.el6 | 0:1.2.16-12.redhat_3.1.ep6.el6 |
| Red Hat:jboss_enterprise_web_server:3.1::el6 | tomcat-native | before 0:1.2.8-10.redhat_10.ep7.el6 | 0:1.2.8-10.redhat_10.ep7.el6 |
| Red Hat:jboss_enterprise_web_server:3.1::el6 | tomcat-native-debuginfo | before 0:1.2.8-10.redhat_10.ep7.el6 | 0:1.2.8-10.redhat_10.ep7.el6 |
| Red Hat:jboss_enterprise_web_server:3.1::el6 | tomcat7 | before 0:7.0.70-22.ep7.el6 | 0:7.0.70-22.ep7.el6 |
| Red Hat:jboss_enterprise_web_server:3.1::el6 | tomcat7-admin-webapps | before 0:7.0.70-22.ep7.el6 | 0:7.0.70-22.ep7.el6 |
+56
Same product
apache: all recordsOther 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 endpointsKEV100Now
- CVE-2021-45046Apache Log4j2 Thread Context Message Pattern and Context Lookup Pattern vulnerable to a denial of service attackKEV96Now
- 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 applic66This week
- CVE-2022-23305SQL injection in JDBC Appender in Apache Log4j V159Plan
- CVE-2021-44832Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration55Plan
- CVE-2022-23302Deserialization of untrusted data in JMSSink in Apache Log4j 1.x54Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Debian:apache-log4j1.2 | 1.2.17-9 · Debian:12 | Package registry (OSV) |
| openSUSE:log4j | 1.2.17-lp151.5.3.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| openSUSE:log4j-mini | 1.2.17-lp151.5.3.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| Red Hat:log4j-eap6 | 0:1.2.16-12.redhat_3.1.ep6.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6 | Package registry (OSV) |
| Red Hat:tomcat-native | 0:1.2.8-10.redhat_10.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6 | Package registry (OSV) |
| Red Hat:tomcat-native-debuginfo | 0:1.2.8-10.redhat_10.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6 | Package registry (OSV) |
| Red Hat:tomcat7 | 0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6 | Package registry (OSV) |
| Red Hat:tomcat7-admin-webapps | 0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6 | Package registry (OSV) |
| Red Hat:tomcat7-docs-webapp | 0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6 | Package registry (OSV) |
| Red Hat:tomcat7-el-2.2-api | 0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6 | Package registry (OSV) |
| Red Hat:tomcat7-javadoc | 0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6 | Package registry (OSV) |
| Red Hat:tomcat7-jsp-2.2-api | 0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6 | Package registry (OSV) |
| Red Hat:tomcat7-jsvc | 0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6 | Package registry (OSV) |
| Red Hat:tomcat7-lib | 0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6 | Package registry (OSV) |
| Red Hat:tomcat7-log4j | 0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6 | Package registry (OSV) |
| SUSE:log4j | 1.2.17-5.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 | Package registry (OSV) |
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 ×3
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.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:78 | 2019-12-25 |
| Proof-of-concept repository on GitHub | stars:1 | 2020-07-16 |
| Proof-of-concept repository on GitHub | stars:39 | 2021-12-14 |
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.
- Published
- First PoC+4 d
- TodaySep 29, 2026+2475 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
Weakness class (CWE)
CWE-502 · Deserialization of Untrusted DataCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.
The bug in code
The whole CWE-502 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
payload = sock.recv(65536)job = pickle.loads(payload)Fixed
payload = sock.recv(65536)if not hmac.compare_digest(sign(payload), header_sig): raise PermissionError("invalid signature")job = JobSchema.validate(json.loads(payload))Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- lists.opensuse.org/opensuse-security-announce/2020-01/msg00022.html
- lists.apache.org/thread.html/277b4b5c2b0e06a825ccec565fa65bd671f35a4d58e3e2ec5d0618e1%40%3Cdev.tika.apache.org%3E
- lists.apache.org/thread.html/44491fb9cc19acc901f7cff34acb7376619f15638439416e3e14761c%40%3Cdev.tika.apache.org%3E
- lists.apache.org/thread.html/479471e6debd608c837b9815b76eab24676657d4444fcfd5ef96d6e6%40%3Cdev.tika.apache.org%3E
- lists.apache.org/thread.html/564f03b4e9511fcba29c68fc0299372dadbdb002718fa8edcc4325e4%40%3Cjira.kafka.apache.org%3E
- lists.apache.org/thread.html/6114ce566200d76e3cc45c521a62c2c5a4eac15738248f58a99f622c%40%3Cissues.activemq.apache.org%3E
- lists.apache.org/thread.html/752ec92cd1e334a639e79bfbd689a4ec2c6579ec5bb41b53ffdf358d%40%3Cdev.kafka.apache.org%3E
- lists.apache.org/thread.html/8ab32b4c9f1826f20add7c40be08909de9f58a89dc1de9c09953f5ac%40%3Cissues.activemq.apache.org%3E
- lists.apache.org/thread.html/eea03d504b36e8f870e8321d908e1def1addda16adda04327fe7c125%40%3Cdev.logging.apache.org%3E
- lists.apache.org/thread.html/r05755112a8c164abc1004bb44f198b1e3d8ca3d546a8f13ebd3aa05f%40%3Cissues.zookeeper.apache.org%3E
- lists.apache.org/thread.html/r107c8737db39ec9ec4f4e7147b249e29be79170b9ef4b80528105a2d%40%3Cdev.zookeeper.apache.org%3E
- lists.apache.org/thread.html/r13d4b5c60ff63f3c4fab51d6ff266655be503b8a1884e2f2fab67c3a%40%3Ccommon-issues.hadoop.apache.org%3E
- lists.apache.org/thread.html/r189aaeaad897f7d6b96f7c43a8ef2dfb9f6e9f8c1cc9ad182ce9b9ae%40%3Cjira.kafka.apache.org%3E
- lists.apache.org/thread.html/r18f1c010b554a3a2d761e8ffffd8674fd4747bcbcf16c643d708318c%40%3Cissues.activemq.apache.org%3E
- lists.apache.org/thread.html/r1b103833cb5bc8466e24ff0ecc5e75b45a705334ab6a444e64e840a0%40%3Cissues.bookkeeper.apache.org%3E
- lists.apache.org/thread.html/r1b7734dfdfd938640f2f5fb6f4231a267145c71ed60cc7faa1cbac07%40%3Ccommon-issues.hadoop.apache.org%3E
- lists.apache.org/thread.html/r26244f9f7d9a8a27a092eb0b2a0ca9395e88fcde8b5edaeca7ce569c%40%3Ccommon-issues.hadoop.apache.org%3E
- lists.apache.org/thread.html/r2721aba31a8562639c4b937150897e24f78f747cdbda8641c0f659fe%40%3Cusers.kafka.apache.org%3E
- lists.apache.org/thread.html/r2756fd570b6709d55a61831ca028405bcb3e312175a60bc5d911c81f%40%3Cjira.kafka.apache.org%3E
- lists.apache.org/thread.html/r2ce8d26154bea939536e6cf27ed02d3192bf5c5d04df885a80fe89b3%40%3Cissues.activemq.apache.org%3E
Vendor advisories and official records. Exploit/PoC links are deliberately left out.