# log4j:log4j (Maven) vulnerabilities

6 known vulnerabilities (2 critical, 4 high), with the versions each affects and the releases that fix them.

## At a glance

- Latest release: not known (cve.now hasn't read this package's releases)
- Newest unaffected release: not known without release data
- Registry: https://central.sonatype.com/artifact/log4j/log4j

## Advisories (6)

### [CVE-2023-26464](https://cve.now/CVE-2023-26464): Apache Log4j 1.x (EOL) allows DoS in Chainsaw and SocketAppender

- Severity: High 7.5
- Published: Mar 10, 2023
- Affected: from 1.0.4, fixed in 2.0.

### [CVE-2022-23307](https://cve.now/CVE-2022-23307): A deserialization flaw in the Chainsaw component of Log4j 1 can lead to malicious code execution.

- Severity: High 8.8
- Published: Jan 18, 2022
- Affected: through 1.2.17.

### [CVE-2022-23305](https://cve.now/CVE-2022-23305): SQL injection in JDBC Appender in Apache Log4j V1

- Severity: Critical 9.8
- Published: Jan 18, 2022
- Affected: through 1.2.17.

### [CVE-2022-23302](https://cve.now/CVE-2022-23302): Deserialization of untrusted data in JMSSink in Apache Log4j 1.x

- Severity: High 8.8
- Published: Jan 18, 2022
- Affected: through 1.2.17.

### [CVE-2021-4104](https://cve.now/CVE-2021-4104): Deserialization of untrusted data in JMSAppender in Apache Log4j 1.2

- Severity: High 7.5
- Published: Dec 14, 2021
- Affected: from 1.2.0, through 1.2.17.

### [CVE-2019-17571](https://cve.now/CVE-2019-17571): Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely…

- Severity: Critical 9.8
- Published: Dec 20, 2019
- Affected: from 1.2, through 1.2.17.

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/packages/maven/log4j:log4j
Site guide for agents: https://cve.now/llms.txt
Uses NVD data; not endorsed by NVD.