CVE-2018-0670

CRITICALNVD 9.89.8—

9.8

INplc-RT 3.08 and earlier allows remote attackers to bypass authentication to execute an arbitrary command through the protocol-compliant traffic. This is a different vulnerability than CVE-2018-0669.

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

Published

January 9, 2019

Last Modified

November 21, 2024

References (4)

vultures@jpcerthttp://www.mnc.co.jp/INplc/info_20180907_E.htm
vultures@jpcerthttps://jvn.jp/en/jp/JVN59624986/index.html
af854a3a-2127-422b-91ae-364da2661108http://www.mnc.co.jp/INplc/info_20180907_E.htm
af854a3a-2127-422b-91ae-364da2661108https://jvn.jp/en/jp/JVN59624986/index.html

Weakness Classification(1)

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

CWE-287Improper Authentication

Data Freshness Timeline

(refreshed 10× in last 7d / 20× 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-04 13:10 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 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-27 23:33 UTCEG score recompute
2026-05-27 23:33 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 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-25 17:16 UTCOSV refresh

Frequently asked(5)

What is CVE-2018-0670?

CVE-2018-0670 is a critical vulnerability published on January 9, 2019. INplc-RT 3.08 and earlier allows remote attackers to bypass authentication to execute an arbitrary command through the protocol-compliant traffic. This is a different vulnerability than CVE-2018-0669.

When was CVE-2018-0670 disclosed?

CVE-2018-0670 was first published in the National Vulnerability Database on January 9, 2019, 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-0670 actively exploited?

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

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

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

How do I remediate CVE-2018-0670?

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

Explore →

Is Your Infrastructure Affected by CVE-2018-0670?

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

Start Free Scan →Browse All CVEs

CVE-2018-0670

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2018-0670?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)