io.atomix:atomix vulnerabilities

Registry
Maven
Latest
3.1.12

7 known advisories

The latest version, 3.1.12, is not affected by any of them. Projects on older versions may be.

Update to the latest version:mvn versions:use-dep-version -Dincludes=io.atomix:atomix -DdepVersion=3.1.12 -DforceVersion=true

Is your project on an affected io.atomix:atomix?

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 io.atomix:atomix

  • MediumCVE-2020-35215GHSA-g7p8-r2ch-4rmf17 Dec 2021

    Malicious Atomix node queries expose sensitive information

    Affected
    <=3.1.5
    Fixed in
    No fix released
  • HighCVE-2020-35209GHSA-7fr2-94h7-ccg217 Dec 2021

    An issue in Atomix v3.1.5 allows unauthorized Atomix nodes to join a target cluster via providing configuration information.

    Affected
    <=3.1.5
    Fixed in
    No fix released
  • HighCVE-2020-35214GHSA-m4h3-7mc2-v29517 Dec 2021

    An issue in Atomix v3.1.5 allows a malicious Atomix node to remove states of ONOS storage via abuse of primitive operations.

    Affected
    <=3.1.5
    Fixed in
    No fix released
  • MediumCVE-2020-35210GHSA-mf27-wg66-m8f517 Dec 2021

    A vulnerability in Atomix v3.1.5 allows attackers to cause a denial of service (DoS) via a Raft session flooding attack using Raft OpenSessionRequest messages.

    Affected
    <=3.1.5
    Fixed in
    No fix released
  • MediumCVE-2020-35216GHSA-6vvh-5794-vpmj17 Dec 2021

    An issue in Atomix v3.1.5 allows attackers to cause a denial of service (DoS) via false member down event messages.

    Affected
    <=3.1.5
    Fixed in
    No fix released
  • HighCVE-2020-35213GHSA-2fqw-684c-pvp717 Dec 2021

    An issue in Atomix v3.1.5 allows attackers to cause a denial of service (DoS) via false link event messages sent to a master ONOS node.

    Affected
    <=3.1.5
    Fixed in
    No fix released
  • HighCVE-2020-35211GHSA-4jhc-wjr3-pwh217 Dec 2021

    An issue in Atomix v3.1.5 allows unauthorized Atomix nodes to become the lead node.

    Affected
    <=3.1.5
    Fixed in
    No fix released

Is your io.atomix:atomix version vulnerable?

Which of your client projects still run an old io.atomix:atomix?

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.