dbcve.org
AtomixApplication

CVE-2020-35209

HIGH · 7.5 CVSS v3.1 Published 2021-12-16
Fix available
A fix is available. Upgrade to after 3.1.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

In Atomix v3.1.5, the cluster membership protocol lacks proper authentication validation, allowing any node that provides configuration information to join the cluster. An unauthenticated or malicious node can exploit this by sending join requests with cluster configuration data, thereby gaining membership and potentially accessing or manipulating distributed data.

MitigationImplement strict node authentication and authorization for cluster membership, such as requiring signed credentials or pre-shared keys, and validate all join requests against an authorized node list before granting cluster membership.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AtomixApplication
Affected:<= 3.1.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Atomix version
    Check your project dependencies (Maven pom.xml, Gradle build.gradle, or JAR manifest) for the atomix dependency version. Run: grep -r 'atomix' pom.xml or check the JAR file version with java -jar your-atomix-jar.jar --version
    Affected if The installed version is 3.1.5 or any earlier version (versions prior to the fixed release)
  2. Verify cluster protocol is in use
    Inspect your Atomix configuration files (usually YAML or JSON in src/main/resources) for cluster-related settings. Look for 'cluster' or 'member' configuration sections that define node addresses and ports
    Affected if Cluster membership protocol is configured and enabled with multiple nodes defined
  3. Examine cluster authentication settings
    Search configuration files for authentication-related properties such as 'authentication', 'credential', 'secure', 'ssl', 'tls', 'key', or 'token' settings within the cluster or member sections
    Affected if No authentication, authorization, or credential validation is configured for cluster membership joins
  4. Review network exposure of cluster ports
    Check your firewall rules and Atomix bind address configuration. Look for 'bind-address', 'bind-port', or 'address' settings in cluster config to identify exposed cluster communication endpoints
    Affected if Cluster communication ports (default 5679-5689 range) are accessible from untrusted networks without network-level access controls
  5. Inspect join request handling
    Review application logs for incoming join requests. Check if the cluster accepts join requests without validating credentials: grep -i 'join' <atomix-log-file> or monitor network traffic on cluster ports
    Affected if Join requests are logged as accepted without evidence of credential validation or authorization checks

You are affected if you are running Atomix version 3.1.5 or earlier with cluster membership enabled and no authentication or authorization controls configured for cluster node joins.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 3.1.5
Interim mitigation

Implement strict node authentication and authorization for cluster membership, such as requiring signed credentials or pre-shared keys, and validate all join requests against an authorized node list before granting cluster membership.

Fix this in Atomix Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-35209 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-35209 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data