Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
HIGH severity

CVE-2020-35211

HIGH

CVE-2020-35211 is a high-severity (CVSS 7.5) vulnerability in io.atomix:atomix. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2020-35211 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Published
Dec 17, 2021
Updated
Dec 3, 2024
Affected
1 pkg
Patched
None yet
Exploits
1 known
Exploitation data as of Dec 3, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
io.atomix:atomix

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

An issue in Atomix v3.1.5 allows unauthorized Atomix nodes to become the lead node in a target cluster via manipulation of the variable terms in RaftContext.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
Mavenio.atomix:atomixall versionsNo fix
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.atomix:atomix. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of io.atomix:atomix has shipped for CVE-2020-35211 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2020-35211 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2020-35211. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue in Atomix v3.1.5 allows unauthorized Atomix nodes to become the lead node in a target cluster via manipulation of the variable terms in RaftContext.
O3 Security · Impact-Aware SCA

Is CVE-2020-35211 in your dependencies?

O3 detects CVE-2020-35211 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

CVE-2020-35211: atomix (High 7.5) | O3 Security