Is org.zenframework.z8.dependencies.commons:log4j-1.2.17 2.0 vulnerable?
Maven · 1 release from 2.0.0 to 2.0.0 · latest org.zenframework.z8.dependencies.commons:log4j-1.2.17 is 2.0 · checked 20 Nov 2026
Yes: 5 known advisories
Yes. org.zenframework.z8.dependencies.commons:log4j-1.2.17 2.0.0, the last 2.0 release, is affected by 5 known security advisories (3 critical, 2 high), including CVE-2022-23305, CVE-2022-23307, CVE-2019-17571. At least one has no fixed release yet.
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
Advisories affecting org.zenframework.z8.dependencies.commons:log4j-1.2.17 2.0.0
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
Which of your client projects are still on org.zenframework.z8.dependencies.commons:log4j-1.2.17 2.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.zenframework.z8.dependencies.commons:log4j-1.2.17 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.