CVE-2018-17900

CRITICALNVD 9.89.8—Trending — 3 sources updated this week

9.8

Yokogawa STARDOM Controllers FCJ, FCN-100, FCN-RTU, FCN-500, All versions R4.10 and prior, The web application improperly protects credentials which could allow an attacker to obtain credentials for remote access to controllers.

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

Published

October 12, 2018

Last Modified

November 21, 2024

References (4)

ics-cert@hqhttps://ics-cert.us-cert.gov/advisories/ICSA-18-151-03
ics-cert@hqhttps://web-material3.yokogawa.com/YSAR-18-0007-E.pdf
af854a3a-2127-422b-91ae-364da2661108https://ics-cert.us-cert.gov/advisories/ICSA-18-151-03
af854a3a-2127-422b-91ae-364da2661108https://web-material3.yokogawa.com/YSAR-18-0007-E.pdf

Weakness Classification(1)

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

CWE-522Insufficiently Protected Credentials

Data Freshness Timeline

(refreshed 12× 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:49 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 02:12 UTCEG score recompute
2026-05-28 02:12 UTCGHSA enrichment
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

Frequently asked(5)

What is CVE-2018-17900?

CVE-2018-17900 is a critical vulnerability published on October 12, 2018. Yokogawa STARDOM Controllers FCJ, FCN-100, FCN-RTU, FCN-500, All versions R4.10 and prior, The web application improperly protects credentials which could allow an attacker to obtain credentials for remote access to controllers.

When was CVE-2018-17900 disclosed?

CVE-2018-17900 was first published in the National Vulnerability Database on October 12, 2018, 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-2018-17900 actively exploited?

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

What is the CVSS score of CVE-2018-17900?

CVE-2018-17900 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2018-17900?

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

Explore →

Is Your Infrastructure Affected by CVE-2018-17900?

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

Start Free Scan →Browse All CVEs

CVE-2018-17900

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2018-17900?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)