CVE-2018-0924Low

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

Published
March 13, 2018
Last Modified
—

🔗 CVE IDs covered (1)

📋 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-0924. This page also shows what EchelonGraph holds for CVE-2018-0924, 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 products6

  • Microsoft Exchange Server 2010 Service Pack 3 Update Rollup 20
  • Microsoft Exchange Server 2013 Cumulative Update 18
  • Microsoft Exchange Server 2013 Cumulative Update 19
  • Microsoft Exchange Server 2013 Service Pack 1
  • Microsoft Exchange Server 2016 Cumulative Update 7
  • Microsoft Exchange Server 2016 Cumulative Update 8

✅ Updates Microsoft lists: 6 updates

6 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—

🧭 EchelonGraph on CVE-2018-0924

EchelonGraph score
6.5 MEDIUM
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

Microsoft Exchange Server 2010 Service Pack 3 Update Rollup 20, Microsoft Exchange Server 2013 Cumulative Update 18, Microsoft Exchange Server 2013 Cumulative Update 19, Microsoft Exchange Server 2013 Service Pack 1, Microsoft Exchange Server 2016 Cumulative Update 7, and Microsoft Exchange Server 2016 Cumulative Update 8 allow an information disclosure vulnerability due to how URL redirects are handled, aka "Microsoft Exchange Information Disclosure Vulnerability". This CVE is unique from CVE-2018-0941.

Published by Microsoft Corporation, the CVE Numbering Authority that assigned CVE-2018-0924, 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 (7)