CVE-2018-6231

CRITICALNVD 9.89.8—

9.8

A server auth command injection authentication bypass vulnerability in Trend Micro Smart Protection Server (Standalone) versions 3.3 and below could allow remote attackers to escalate privileges on vulnerable installations.

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

Published

March 15, 2018

Last Modified

November 21, 2024

References (4)

security@trendmicrohttps://success.trendmicro.com/solution/1119385
security@trendmicrohttps://www.zerodayinitiative.com/advisories/ZDI-18-218/
af854a3a-2127-422b-91ae-364da2661108https://success.trendmicro.com/solution/1119385
af854a3a-2127-422b-91ae-364da2661108https://www.zerodayinitiative.com/advisories/ZDI-18-218/

Weakness Classification(1)

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

CWE-78OS Command Injection

Data Freshness Timeline

(refreshed 9× 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-04 13:10 UTCepss_batch
2026-06-04 13:10 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:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:42 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-23 02:16 UTCEG score recompute
2026-05-23 02:16 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2018-6231?

CVE-2018-6231 is a critical vulnerability published on March 15, 2018. A server auth command injection authentication bypass vulnerability in Trend Micro Smart Protection Server (Standalone) versions 3.3 and below could allow remote attackers to escalate privileges on vulnerable installations.

When was CVE-2018-6231 disclosed?

CVE-2018-6231 was first published in the National Vulnerability Database on March 15, 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-6231 actively exploited?

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

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

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

How do I remediate CVE-2018-6231?

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

Explore →

Is Your Infrastructure Affected by CVE-2018-6231?

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

Start Free Scan →Browse All CVEs

CVE-2018-6231

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2018-6231?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)