KB5000800: Windows Server Security Update (March 2021)
Microsoft Internet Explorer contains an unspecified vulnerability that allows for memory corruption.
A remote attacker, without authentication, can achieve partial data exposure, arbitrary modification of data, partial service disruption. CISA has confirmed use of this vulnerability in known ransomware campaigns — treat as high priority for remediation. Federal agencies are required to remediate by 2021-11-17 under CISA BOD 22-01.
This is a Use After Free (CWE-416) vulnerability in Microsoft Internet Explorer. Exploitation requires remote network access, low attack complexity, no authentication required, and user interaction required.
📧
Phishing link
🖼
Malicious file
🔓
Server compromised
Probably yes if any of these apply:
CISA confirms this CVE has been used in known ransomware campaigns. Added to the KEV catalog on 2021-11-03; federal agencies required to remediate by 2021-11-17.
Manual download
For air-gapped servers or out-of-band deployment. Microsoft Update Catalog returns every OS-version variant of this update.
↗ Microsoft Update CatalogKB5000800Manual remediation steps
Apply the Microsoft Security Update
Microsoft has released an official security update that fixes this vulnerability.
Required KB Updates
Supersedes: KB4601313, KB4601315, KB4601318, KB4601319, KB4601331, KB4601345, KB4601347, KB4601348, KB4601354, KB4601360, KB4601384
Affected Products
Installation Methods
Windows Update (recommended)
Microsoft Update Catalog (manual download)
.msu installer with administrator privilegesWSUS / SCCM / Intune
Approve KB5000800 for the affected products in your update management console.
Microsoft Download Center Links
Verification
Confirm the update is installed:
Get-HotFix | Where-Object { $_.HotFixID -in @('KB5000800','KB5000802','KB5000803','KB5000807','KB5000808','KB5000809','KB5000822','KB5000841','KB5000844','KB5000847','KB5000848') }
References
Discovery Credit
yangkang(@dnpushme) & huangyi(@C0rk1_H), Enki
No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.