CVE-2018-8154Critical

Microsoft security update for CVE-2018-8154 — Microsoft Exchange Server

Published
May 8, 2018
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2018-8154 →

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2018-8154. This page also shows what EchelonGraph holds for CVE-2018-8154, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products7

  • Microsoft Exchange Server 2010 Service Pack 3 Update Rollup 21
  • Microsoft Exchange Server 2010 Service Pack 3 Update Rollup 24
  • Microsoft Exchange Server 2013 Cumulative Update 19
  • Microsoft Exchange Server 2013 Cumulative Update 20
  • Microsoft Exchange Server 2013 Service Pack 1
  • Microsoft Exchange Server 2016 Cumulative Update 8
  • Microsoft Exchange Server 2016 Cumulative Update 9

✅ Updates Microsoft lists: 7 updates

7 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update—
—Security Update—
—Security Update—
—Security Update—
—Security Update—
—Security Update—
—Security Update—

🧭 EchelonGraph on CVE-2018-8154

EchelonGraph score
9.8 CRITICAL
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

A remote code execution vulnerability exists in Microsoft Exchange software when the software fails to properly handle objects in memory, aka "Microsoft Exchange Memory Corruption Vulnerability." This affects Microsoft Exchange Server. This CVE ID is unique from CVE-2018-8151.

Published by Microsoft Corporation, the CVE Numbering Authority that assigned CVE-2018-8154, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (8)