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?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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

  • HighCVE-2022-23302GHSA-w9p3-5cr8-m3jj21 Jan 2022

    Deserialization of Untrusted Data in Log4j 1.x

    Affected
    <=2.0
    Fixed in
    No fix released
  • CriticalCVE-2022-23305GHSA-65fg-84f6-3jq321 Jan 2022

    SQL Injection in Log4j 1.2.x

    Affected
    <=2.0
    Fixed in
    No fix released
  • CriticalCVE-2022-23307GHSA-f7vh-qwp3-x37m19 Jan 2022

    Deserialization of Untrusted Data in Apache Log4j

    Affected
    <=2.0
    Fixed in
    No fix released
  • HighCVE-2021-4104GHSA-fp5r-v3w9-433314 Dec 2021

    JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data

    Affected
    <=2.0
    Fixed in
    No fix released
  • CriticalCVE-2019-17571GHSA-2qrg-x229-3v8q6 Jan 2020

    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.