org.apache.logging.log4j:log4j-core vulnerabilities
A versatile, industrial-grade, and reference implementation of the Log4j API. It bundles a rich set of components to assist various use cases: Appenders targeting files, network sockets, databases, SMTP servers; Layouts that can render CSV, HTML, JSON, Syslog, etc. formatted outputs; Filters that can be configured using log event rates, regular expressions, scripts, time, etc. It contains several extension points to introduce custom components, if needed.
- Registry
- Maven
- Latest
- 2.26.1
- License
- Apache-2.0
12 known advisories
The latest version, 2.26.1, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.apache.logging.log4j:log4j-core -DdepVersion=2.26.1 -DforceVersion=trueIs your project on an affected org.apache.logging.log4j:log4j-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.apache.logging.log4j:log4j-core
Apache Log4j 1 to Log4j 2 bridge: silent log event loss in Log4j1XmlLayout due to unescaped XML 1.0 forbidden characters
- Affected
- >=2.7 <2.25.4 · >=3.0.0-beta1 <=3.0.0-beta2
- Fixed in
- 2.25.4
Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters
- Affected
- >=2.0-alpha1 <2.25.4 · >=3.0.0-alpha1 <=3.0.0-beta3
- Fixed in
- 2.25.4
Apache Log4j Core: log injection in `Rfc5424Layout` due to silent configuration incompatibility
- Affected
- >=2.21.0 <2.25.4 · >=3.0.0-beta1 <=3.0.0-beta3
- Fixed in
- 2.25.4
Apache Log4j Core: `verifyHostName` attribute silently ignored in TLS configuration
- Affected
- >=2.12.0 <2.25.4 · >=3.0.0-alpha1 <=3.0.0-beta3
- Fixed in
- 2.25.4
Apache Log4j does not verify the TLS hostname in its Socket Appender
- Affected
- >=2.0-beta9 <2.25.3
- Fixed in
- 2.25.3
Apache Log4j 1.x (EOL) allows Denial of Service (DoS)
- Affected
- >=1.0.4 <2.0
- Fixed in
- 2.0
Improper Input Validation and Injection in Apache Log4j2
- Affected
- >=2.0-beta7 <2.3.2 · >=2.4 <2.12.4 · >=2.13.0 <2.17.1
- Fixed in
- 2.3.2, 2.12.4, 2.17.1
Apache Log4j2 vulnerable to Improper Input Validation and Uncontrolled Recursion
- Affected
- >=2.4.0 <2.12.3 · >=2.13.0 <2.17.0 · <2.3.1
- Fixed in
- 2.3.1, 2.12.3, 2.17.0
Incomplete fix for Apache Log4j vulnerability
- Affected
- >=2.13.0 <2.16.0 · >=2.4.0 <2.12.2 · <2.3.1
- Fixed in
- 2.3.1, 2.12.2, 2.16.0
Remote code injection in Log4j
- Affected
- >=2.13.0 <2.15.0 · >=2.0-beta9 <2.3.1 · >=2.4 <2.12.2
- Fixed in
- 2.3.1, 2.12.2, 2.15.0
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender
- Affected
- >=2.13.0 <2.13.2 · >=2.4.0 <2.12.3 · <2.3.2
- Fixed in
- 2.3.2, 2.12.3, 2.13.2
Deserialization of Untrusted Data in Log4j
- Affected
- >=2.0 <2.8.2
- Fixed in
- 2.8.2
Is your org.apache.logging.log4j:log4j-core version vulnerable?
- org.apache.logging.log4j:log4j-core 2.26No known advisories in 2.26.1
- org.apache.logging.log4j:log4j-core 2.25No known advisories in 2.25.5
- org.apache.logging.log4j:log4j-core 2.245 advisories in 2.24.3
- org.apache.logging.log4j:log4j-core 2.235 advisories in 2.23.1
- org.apache.logging.log4j:log4j-core 2.225 advisories in 2.22.1
- org.apache.logging.log4j:log4j-core 2.215 advisories in 2.21.1
Which of your client projects still run an old org.apache.logging.log4j:log4j-core?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.