CVE-2023-36422

7.8 HIGH

📋 TL;DR

This vulnerability in Microsoft Windows Defender allows attackers to elevate privileges on affected systems. An authenticated attacker could exploit this to gain SYSTEM-level access. All Windows systems with vulnerable Windows Defender versions are affected.

💻 Affected Systems

Products:
  • Microsoft Windows Defender
Versions: Specific versions not detailed in CVE; typically affects multiple Windows versions with vulnerable Defender builds
Operating Systems: Windows 10, Windows 11, Windows Server 2016, Windows Server 2019, Windows Server 2022
Default Config Vulnerable: ⚠️ Yes
Notes: Requires Windows Defender to be enabled and running; affects standard configurations.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attacker gains full SYSTEM privileges, enabling complete system compromise, data theft, persistence establishment, and lateral movement across the network.

🟠

Likely Case

Privileged attacker escalates from standard user to administrator or SYSTEM, enabling installation of malware, credential harvesting, and bypassing security controls.

🟢

If Mitigated

With proper patch management and least privilege principles, impact is limited to isolated systems with minimal lateral movement potential.

🌐 Internet-Facing: LOW - This requires local access or authenticated remote access, not directly exploitable from the internet.
🏢 Internal Only: HIGH - Internal attackers or compromised accounts can exploit this to escalate privileges and move laterally.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires authenticated access and specific conditions; not trivial but feasible for skilled attackers.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check Microsoft Security Update Guide for specific KB numbers

Vendor Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36422

Restart Required: Yes

Instructions:

1. Apply latest Windows security updates via Windows Update. 2. For enterprise: Deploy patches through WSUS or SCCM. 3. Verify Defender version is updated post-patch.

🔧 Temporary Workarounds

Disable Windows Defender (Not Recommended)

windows

Temporarily disable Windows Defender to remove attack surface, but leaves system unprotected.

Set-MpPreference -DisableRealtimeMonitoring $true

🧯 If You Can't Patch

  • Implement strict least privilege: Ensure users run with minimal necessary permissions.
  • Monitor for privilege escalation attempts using Windows Event Logs and EDR solutions.

🔍 How to Verify

Check if Vulnerable:

Check Windows Defender version and compare with patched versions in Microsoft advisory.

Check Version:

Get-MpComputerStatus | Select AntivirusSignatureVersion

Verify Fix Applied:

Verify Windows Update history shows relevant security update installed and Defender is running latest version.

📡 Detection & Monitoring

Log Indicators:

  • Windows Event ID 4688 (process creation) with unusual parent-child relationships
  • Defender service crashes or unexpected behavior
  • Privilege escalation patterns in security logs

Network Indicators:

  • Unusual outbound connections from Defender processes
  • Lateral movement attempts post-exploitation

SIEM Query:

EventID=4688 AND (ProcessName="MsMpEng.exe" OR ParentProcessName="MsMpEng.exe") AND NewProcessName contains "cmd.exe" OR "powershell.exe"

🔗 References

📤 Share & Export