CVE-2023-29367

7.8 HIGH

📋 TL;DR

This vulnerability allows remote attackers to execute arbitrary code on systems running the iSCSI Target WMI Provider. Attackers can exploit this without authentication to gain SYSTEM privileges on affected Windows servers. Organizations using Windows Server with iSCSI Target roles are primarily affected.

💻 Affected Systems

Products:
  • Windows Server
Versions: Windows Server 2019, Windows Server 2022
Operating Systems: Windows Server 2019, Windows Server 2022
Default Config Vulnerable: ✅ No
Notes: Only vulnerable when iSCSI Target role is installed and configured. Not present in default installations.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full system compromise with SYSTEM privileges, enabling complete control over the server, data theft, lateral movement, and persistence establishment.

🟠

Likely Case

Remote code execution leading to malware deployment, ransomware attacks, or credential harvesting from the compromised server.

🟢

If Mitigated

Limited impact due to network segmentation, proper access controls, and monitoring preventing successful exploitation.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Microsoft rates this as 'Exploitation More Likely' in their advisory. No public exploit code available as of knowledge cutoff.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Security updates for May 2023 or later

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

Restart Required: Yes

Instructions:

1. Apply May 2023 security updates for Windows Server 2019/2022. 2. Restart affected systems. 3. Verify patch installation via Windows Update history or version check.

🔧 Temporary Workarounds

Disable iSCSI Target Service

windows

Stop and disable the iSCSI Target service if not required

Stop-Service -Name WinTarget
Set-Service -Name WinTarget -StartupType Disabled

Block Network Access

windows

Restrict network access to iSCSI Target ports (default TCP 3260)

New-NetFirewallRule -DisplayName "Block iSCSI" -Direction Inbound -LocalPort 3260 -Protocol TCP -Action Block

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate iSCSI servers from untrusted networks
  • Apply principle of least privilege and monitor for suspicious WMI activity

🔍 How to Verify

Check if Vulnerable:

Check if iSCSI Target role is installed: Get-WindowsFeature -Name iSCSITarget-Server

Check Version:

systeminfo | findstr /B /C:"OS Name" /C:"OS Version"

Verify Fix Applied:

Verify May 2023 security updates are installed: Get-HotFix -Id KB5026361 (Server 2022) or KB5026362 (Server 2019)

📡 Detection & Monitoring

Log Indicators:

  • Unusual WMI activity in Event Logs (Event ID 5857, 5858)
  • Failed authentication attempts to iSCSI service

Network Indicators:

  • Unexpected connections to TCP port 3260 from untrusted sources
  • Anomalous WMI traffic patterns

SIEM Query:

source="windows" AND (event_id=5857 OR event_id=5858) AND process_name="wmiprvse.exe"

🔗 References

📤 Share & Export