CVE-2020-35213

HIGHNVD 8.18.1—

8.1

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.

CVSS v3: 8.1
EG Score: 8.1(medium)
EPSS: 58.7%
KEV: Not listed

Published

December 16, 2021

Last Modified

November 21, 2024

References (2)

cve@mitrehttps://docs.google.com/presentation/d/1i8tVVGE8z9Rtl9UTwktOJpkZwT4kBVLgIk307qMiw_8/edit?usp=sharing
af854a3a-2127-422b-91ae-364da2661108https://docs.google.com/presentation/d/1i8tVVGE8z9Rtl9UTwktOJpkZwT4kBVLgIk307qMiw_8/edit?usp=sharing

Patch Availability(1)

Vendor / Ecosystem	Fixed in / Patch	Released	Source
maven	io.atomix:atomix	—	ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)

Maven(1)

Package	Vulnerable range	Fixed in	Dependents
io.atomix:atomix	0.1.0-beta1 ... 3.1.5 (96 versions)	—	—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component (Injection)

Data Freshness Timeline

(refreshed 10× in last 7d / 18× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 06:10 UTCEG score recompute
2026-05-26 06:10 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2020-35213?

CVE-2020-35213 is a high vulnerability published on December 16, 2021. 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.

When was CVE-2020-35213 disclosed?

CVE-2020-35213 was first published in the National Vulnerability Database on December 16, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2020-35213 actively exploited?

CVE-2020-35213 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 58.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2020-35213?

CVE-2020-35213 has a CVSS v3 base score of 8.1 (NVD).

How do I remediate CVE-2020-35213?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-35213, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-35213

Explore →

Is Your Infrastructure Affected by CVE-2020-35213?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2020-35213

Published

Last Modified

References (2)

Patch Availability(1)

Affected Packages

Weakness Classification(1)

Data Freshness Timeline

Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2020-35213?

Same product

Same CWE

CVE-2020-35213

📅 Published

🔄 Last Modified

🔗 References (2)

Patch Availability(1)

Affected Packages

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2020-35213?

🔗 Related CVEs(same product + same CWE)

Same product

Same CWE

Published

Last Modified

References (2)

Frequently asked(5)

Related CVEs(same product + same CWE)