CVE-2020-35211: Unauthorized Atomix Nodes can Become Lead Node in Atomix v3.1.5

io.atomix:atomix Updated 02 Oct 2025

Summary

17/12/2021
No i
High
7.5

CVE-2020-35211: An issue in Atomix v3.1.5 allows unauthorized Atomix nodes to become the lead node. Affects io.atomix:atomix versions < 3.1.5. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Atomix is a Maven package that provides a distributed coordination framework for building fault-tolerant and highly available applications. It utilizes the Raft consensus algorithm to ensure consistency and fault tolerance in distributed systems. The vulnerability identified in Atomix v3.1.5 allows unauthorized Atomix nodes to become the lead node in a target cluster by manipulating the variable terms in RaftContext.

Vulnerability Detail

The vulnerability in Atomix v3.1.5 enables unauthorized Atomix nodes to take control as the lead node within a cluster. By manipulating the variable terms in RaftContext, an attacker can gain unauthorized access and potentially disrupt the cluster's operations. This can lead to a loss of data consistency and availability, compromising the integrity and reliability of the distributed system.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to apply the recommended fix by upgrading to a patched version of Atomix.

Conclusion

In conclusion, the vulnerability in Atomix v3.1.5 allows unauthorized Atomix nodes to become the lead node in a cluster, potentially compromising data consistency and availability. To mitigate this vulnerability, it is crucial to upgrade to a patched version of Atomix beyond 3.1.5. For further support and assistance with vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for io.atomix:atomix →

Share this vulnerability

FAQ

Atomix is a distributed coordination framework for building fault-tolerant and highly available applications.

The vulnerability allows unauthorized Atomix nodes to become the lead node in a cluster, potentially compromising data consistency and availability.

To fix this vulnerability, upgrade to a patched version of Atomix beyond 3.1.5.

No, there is no known workaround. Upgrading to a patched version is the recommended solution.

For more information, you can refer to the GitHub advisory database and the provided CVE identifier.

Related vulnerabilities

Recent vulnerabilities recorded for io.atomix:atomix.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback