{"answers":{"affected":"2 open source packages ship an affected version, including io.atomix:atomix. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35211 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-35211 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-35211 is a high-severity authentication bypass vulnerability in n/a, published on 16 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-35211 and fix it if it is affected.\n\nWhat it is: CVE-2020-35211 is a high-severity authentication bypass vulnerability in n/a, published on 16 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-35211 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.atomix:atomix (Maven): affected all versions up to 3.1.5; no fix listed\n- io.atomix:atomix (Maven): affected all versions up to 3.1.5; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-35211/ (Markdown: https://insights.sbomify.com/CVE-2020-35211/index.md)","id":"CVE-2020-35211","markdown":"https://insights.sbomify.com/CVE-2020-35211/index.md","name":"CVE-2020-35211","record":{"aliases":["GHSA-4jhc-wjr3-pwh2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Java distributed systems library","requires_auth":"none","summary":"Attackers can manipulate Raft terms to become the lead node in an Atomix cluster, gaining unauthorized control over the distributed system.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"atomix","vendor":"atomix"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"An issue in Atomix v3.1.5 allows unauthorized Atomix nodes to become the lead node.","id":"CVE-2020-35211","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":2,"n_references":1,"next":{"headline":"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.","id":"CVE-2020-35213"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["3.1.5"],"package":"io.atomix:atomix","purl":null,"source":"GHSA-4jhc-wjr3-pwh2"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["3.1.5"],"package":"io.atomix:atomix","purl":"pkg:maven/io.atomix/atomix","source":"GHSA-4jhc-wjr3-pwh2"}],"prev":{"headline":"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.","id":"CVE-2020-35210"},"products":["n/a"],"published":"2021-12-16","related":[{"cvss_score":8.1,"headline":"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.","id":"CVE-2020-35213","kev_date_added":null,"published":"2021-12-16"},{"cvss_score":8.1,"headline":"An issue in Atomix v3.1.5 allows a malicious Atomix node to remove states of ONOS storage via abuse of primitive operations.","id":"CVE-2020-35214","kev_date_added":null,"published":"2021-12-16"},{"cvss_score":7.5,"headline":"An issue in Atomix v3.1.5 allows unauthorized Atomix nodes to join a target cluster via providing configuration information.","id":"CVE-2020-35209","kev_date_added":null,"published":"2021-12-16"},{"cvss_score":6.5,"headline":"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.","id":"CVE-2020-35210","kev_date_added":null,"published":"2021-12-16"},{"cvss_score":6.5,"headline":"Malicious Atomix node queries expose sensitive information","id":"CVE-2020-35215","kev_date_added":null,"published":"2021-12-16"},{"cvss_score":5.9,"headline":"An issue in Atomix v3.1.5 allows attackers to cause a denial of service (DoS) via false member down event messages.","id":"CVE-2020-35216","kev_date_added":null,"published":"2021-12-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can manipulate Raft terms to become the lead node in an Atomix cluster, gaining unauthorized control over the distributed system.","url":"https://insights.sbomify.com/CVE-2020-35211/"}