KB5023696: Windows Server Security Update (March 2023)
Microsoft Windows SmartScreen contains a security feature bypass vulnerability that could allow an attacker to evade Mark of the Web (MOTW) defenses via a specially crafted malicious file.
A local attacker, without authentication, can achieve partial data exposure, partial data tampering, 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 2023-04-04 under CISA BOD 22-01.
This is a Incorrect Authorization (CWE-863) vulnerability in Microsoft Windows. Windows SmartScreen Security Feature Bypass Vulnerability Exploitation requires local access, low attack complexity, no authentication required, and user interaction required.
Probably yes if any of these apply:
CISA confirms this CVE has been used in known ransomware campaigns. Added to the KEV catalog on 2023-03-14; federal agencies required to remediate by 2023-04-04.
Manual download
For air-gapped servers or out-of-band deployment. Microsoft Update Catalog returns every OS-version variant of this update.
↗ Microsoft Update CatalogKB5023696Manual remediation steps
Apply the Microsoft Security Update
Microsoft has released an official security update that fixes this vulnerability.
Required KB Updates
Supersedes: KB5022834, KB5022836, KB5022838, KB5022840, KB5022842, KB5022845
Affected Products
Fixed Build Numbers
Installation Methods
Windows Update (recommended)
Microsoft Update Catalog (manual download)
.msu installer with administrator privilegesWSUS / SCCM / Intune
Approve KB5023696 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 @('KB5023696','KB5023697','KB5023698','KB5023702','KB5023705','KB5023706','KB5023786') }
References
Discovery Credit
Bill Demirkapi of Microsoft, Benoît Sevens and Vlad Stolyarov of Google’s Threat Analysis Group
No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.