CVE-2017-20039

CRITICALNVD 9.89.8—

9.8

A vulnerability was found in SICUNET Access Controller 0.32-05z. It has been classified as very critical. This affects an unknown part. The manipulation leads to weak authentication. It is possible to initiate the attack remotely.

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 61.1%
KEV: Not listed

Published

June 11, 2022

Last Modified

November 21, 2024

References (4)

cna@vuldbhttp://seclists.org/fulldisclosure/2017/Mar/25
cna@vuldbhttps://vuldb.com/?id.98907
af854a3a-2127-422b-91ae-364da2661108http://seclists.org/fulldisclosure/2017/Mar/25
af854a3a-2127-422b-91ae-364da2661108https://vuldb.com/?id.98907

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 8× 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-05-27 13:38 UTCepss_batch
2026-05-27 13:38 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-25 20:48 UTCEG score recompute
2026-05-25 20:48 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2017-20039?

CVE-2017-20039 is a critical vulnerability published on June 11, 2022. A vulnerability was found in SICUNET Access Controller 0.32-05z. It has been classified as very critical. This affects an unknown part. The manipulation leads to weak authentication. It is possible to initiate the attack remotely.

When was CVE-2017-20039 disclosed?

CVE-2017-20039 was first published in the National Vulnerability Database on June 11, 2022, 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-2017-20039 actively exploited?

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

What is the CVSS score of CVE-2017-20039?

CVE-2017-20039 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2017-20039?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-20039, 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-2017-20039

Explore →

Is Your Infrastructure Affected by CVE-2017-20039?

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

Start Free Scan →Browse All CVEs

CVE-2017-20039

📅 Published

🔄 Last Modified

🔗 References (4)