org.zenframework.z8.dependencies.commons:log4j-1.2.17 vulnerabilities
- Registry
- Maven
- Latest
- 2.0
5 known advisories
The latest version, 2.0, is affected by 5 of them.
Is your project on an affected org.zenframework.z8.dependencies.commons:log4j-1.2.17?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.zenframework.z8.dependencies.commons:log4j-1.2.17
Deserialization of Untrusted Data in Log4j 1.x
- Affected
- <=2.0
- Fixed in
- No fix released
SQL Injection in Log4j 1.2.x
- Affected
- <=2.0
- Fixed in
- No fix released
Deserialization of Untrusted Data in Apache Log4j
- Affected
- <=2.0
- Fixed in
- No fix released
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data
- Affected
- <=2.0
- Fixed in
- No fix released
Deserialization of Untrusted Data in Log4j
- Affected
- 2.0
- Fixed in
- No fix released
Is your org.zenframework.z8.dependencies.commons:log4j-1.2.17 version vulnerable?
Which of your client projects still run an old org.zenframework.z8.dependencies.commons:log4j-1.2.17?
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.