CVE-2023-36006

8.8 HIGH

📋 TL;DR

This vulnerability allows remote code execution through the Microsoft WDAC OLE DB provider for SQL Server. An attacker could exploit this to execute arbitrary code on affected systems. Organizations using SQL Server with WDAC OLE DB provider are affected.

💻 Affected Systems

Products:
  • Microsoft SQL Server
Versions: Multiple versions - check Microsoft advisory for specific affected versions
Operating Systems: Windows Server
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WDAC OLE DB provider to be enabled and accessible

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full system compromise allowing attacker to execute arbitrary code with SQL Server service account privileges, potentially leading to data theft, ransomware deployment, or complete system takeover.

🟠

Likely Case

Attacker gains initial foothold on database server, then moves laterally within the network to access sensitive data or deploy additional payloads.

🟢

If Mitigated

Attack contained to isolated database server segment with minimal privileges, preventing lateral movement and limiting data exposure.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires specific conditions and knowledge of the target environment

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apply latest security updates from Microsoft

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

Restart Required: Yes

Instructions:

1. Download and install the latest security update for SQL Server from Microsoft Update Catalog. 2. Restart SQL Server services. 3. Verify the patch is applied successfully.

🔧 Temporary Workarounds

Disable WDAC OLE DB Provider

windows

Temporarily disable the vulnerable component if not required for operations

Use SQL Server Configuration Manager to disable WDAC OLE DB provider

Network Segmentation

all

Restrict network access to SQL Server ports

Configure firewall rules to limit access to SQL Server (default port 1433)

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate SQL Server from untrusted networks
  • Apply principle of least privilege to SQL Server service accounts and database users

🔍 How to Verify

Check if Vulnerable:

Check SQL Server version and installed updates against Microsoft's security bulletin

Check Version:

SELECT @@VERSION;

Verify Fix Applied:

Verify that the security update KB number from Microsoft advisory is installed

📡 Detection & Monitoring

Log Indicators:

  • Unusual OLE DB provider usage patterns
  • Failed authentication attempts to SQL Server
  • Suspicious process creation from SQL Server service

Network Indicators:

  • Unusual network connections to SQL Server ports
  • Suspicious SQL queries from unexpected sources

SIEM Query:

source="sql_server" AND (event_id=18456 OR event_id=33205) AND user!="NT AUTHORITY\SYSTEM"

🔗 References

📤 Share & Export