Skip to content
Fencer Intel
high 7.5

CVE-2020-35211 json

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

published 4y ago modified 4mo ago also GHSA-4jhc-wjr3-pwh2 , EUVD-2021-2439

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits
0
none known

Summary

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.

Is CVE-2020-35211 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-35211 updated cvss 7.5

atomix: Atomix 3.1.5 allows unauthorized Atomix nodes to become the lead node in a target cluster

  • Red Hat Fuse 7 atomix atomix Red Hat Integration Camel K 1 atomix atomix
    affected: no fix planned “Will not fix”
  • Red Hat build of Quarkus io.quarkus.platform-quarkus-platform-config io.quarkus.platform-quarkus-platform-config Red Hat Integration Camel Quarkus 1 atomix atomix
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.07% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • docs.google.com https://docs.google.com/presentation/d/1C_IpRfSU-9FMezcHCFZ-qg-15JO-W36yvqcnzI8sQs8/edit?usp=sharing referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven io.atomix:atomix
<=3.1.5
 no fix listed

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.