CVE-2024-29984

8.8 HIGH

📋 TL;DR

This vulnerability in Microsoft OLE DB Driver for SQL Server allows remote attackers to execute arbitrary code on affected systems by sending specially crafted requests. It affects applications using this driver to connect to SQL Server databases. Attackers could gain full control of vulnerable systems.

💻 Affected Systems

Products:
  • Microsoft OLE DB Driver for SQL Server
Versions: All versions prior to the April 2024 security update
Operating Systems: Windows
Default Config Vulnerable: ⚠️ Yes
Notes: Applications using the vulnerable OLE DB driver component are affected regardless of SQL Server version. Both 32-bit and 64-bit versions are vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise leading to data theft, ransomware deployment, or persistent backdoor installation across the network.

🟠

Likely Case

Attacker gains SYSTEM-level privileges on the vulnerable machine, enabling lateral movement, credential harvesting, and data exfiltration.

🟢

If Mitigated

Limited impact due to network segmentation, application sandboxing, and least-privilege configurations preventing full system takeover.

🌐 Internet-Facing: HIGH if vulnerable applications are exposed to the internet, as exploitation requires only network access to the service.
🏢 Internal Only: HIGH due to potential for lateral movement and privilege escalation within corporate networks.

🎯 Exploit Status

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

Microsoft rates this as 'Exploitation More Likely' in their advisory. The vulnerability requires no authentication and has low attack complexity.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: April 2024 security update (specific version depends on driver edition)

Vendor Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-29984

Restart Required: Yes

Instructions:

1. Download the April 2024 security update from Microsoft Update Catalog. 2. Apply the update to all systems using OLE DB Driver for SQL Server. 3. Restart affected systems and applications. 4. Test application functionality after patching.

🔧 Temporary Workarounds

Network Segmentation

all

Restrict network access to applications using OLE DB Driver to only necessary clients and SQL Server instances.

Application Sandboxing

windows

Run applications using the vulnerable driver with reduced privileges and in isolated environments.

🧯 If You Can't Patch

  • Implement strict network access controls to limit exposure to trusted sources only
  • Monitor for unusual process creation or network connections from applications using OLE DB Driver

🔍 How to Verify

Check if Vulnerable:

Check the driver version in Programs and Features or via PowerShell: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*OLE DB Driver*'} | Select Name, Version

Check Version:

powershell -Command "Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*OLE DB Driver*'} | Select Name, Version"

Verify Fix Applied:

Verify the driver version is updated to April 2024 or later security update version

📡 Detection & Monitoring

Log Indicators:

  • Unusual process creation from SQL client applications
  • Access violations or memory corruption events in application logs
  • Failed authentication attempts followed by successful connections

Network Indicators:

  • Unusual SQL protocol traffic patterns
  • Connection attempts to SQL Server from unexpected sources
  • Large or malformed SQL protocol packets

SIEM Query:

source="*security*" OR source="*application*" ("OLE DB" OR "SQLNCLI") AND ("access violation" OR "memory corruption" OR "unhandled exception")

🔗 References

📤 Share & Export