Microsoft WDAC SQL Server ODBC Driver Remote Code Execution Vulnerability
🔗 CVE IDs covered (1)
📋 Description
According to the CVSS metric, the attack vector is network (AV:N) and the user interaction is required (UI:R). What is the target context of the remote code execution? An authenticated victim who is connected to the network must be tricked or persuaded to connect to a malicious SQL database using their SQL client application. After the connection is made, the server can send specially crafted replies to the client that exploit the vulnerability and permit execution of arbitrary code within the context of the user's SQL client application.
According to the CVSS metric, user interaction is required (UI:R). What interaction would the user have to do? An attacker could exploit the vulnerability by tricking an authenticated user (CVSS metric UI:R) into attempting to connect to a malicious SQL server via a connection driver (for example: ODBC and / or OLEDB as applicable).
How could an attacker exploit this vulnerability? An attacker could exploit the vulnerability by tricking an authenticated user (CVSS metric UI:R) into attempting to connect to a malicious SQL server via OLEDB (CVSS metric AV:N), which could result in the server receiving a malicious networking packet. This could allow the attacker to execute code remotely on the client.
🎯 Affected products36
- Windows 10 Version 1607 for 32-bit Systems
- Windows 10 Version 1607 for x64-based Systems
- Windows 10 Version 1809 for 32-bit Systems
- Windows 10 Version 1809 for ARM64-based Systems
- Windows 10 Version 1809 for x64-based Systems
- Windows 10 Version 21H2 for 32-bit Systems
- Windows 10 Version 21H2 for ARM64-based Systems
- Windows 10 Version 21H2 for x64-based Systems
- Windows 10 Version 22H2 for 32-bit Systems
- Windows 10 Version 22H2 for ARM64-based Systems
- Windows 10 Version 22H2 for x64-based Systems
- Windows 10 for 32-bit Systems
- Windows 10 for x64-based Systems
- Windows 11 Version 22H2 for ARM64-based Systems
- Windows 11 Version 22H2 for x64-based Systems
- Windows 11 Version 23H2 for ARM64-based Systems
- Windows 11 Version 23H2 for x64-based Systems
- Windows 11 version 21H2 for ARM64-based Systems
- Windows 11 version 21H2 for x64-based Systems
- Windows Server 2008 R2 for x64-based Systems Service Pack 1
- Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
- Windows Server 2008 for 32-bit Systems Service Pack 2
- Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)
- Windows Server 2008 for x64-based Systems Service Pack 2
- Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)
- Windows Server 2012
- Windows Server 2012 (Server Core installation)
- Windows Server 2012 R2
- Windows Server 2012 R2 (Server Core installation)
- Windows Server 2016
- +6 more not shown
✅ Remediation
KB5036896 (Security Update) — fixed build 10.0.17763.5696 KB5036909 (Security Update) — fixed build 10.0.20348.2402 KB5036894 (Security Update) — fixed build 10.0.22000.2899 KB5036892 (Security Update) — fixed build 10.0.19044.4291 KB5036893 (Security Update) — fixed build 10.0.22621.3447 KB5036892 (Security Update) — fixed build 10.0.19045.4291 KB5036893 (Security Update) — fixed build 10.0.22631.3447 KB5036910 (Security Update) — fixed build 10.0.25398.830 KB5036925 (Security Update) — fixed build 10.0.10240.20596 KB5036899 (Security Update) — fixed build 10.0.14393.6897 KB5036932 (Monthly Rollup) — fixed build 6.0.6003.22618 KB5036950 (Security Only) — fixed build 6.0.6003.22618 KB5036967 (Monthly Rollup) — fixed build 6.1.7601.27067 KB5036922 (Security Only) — fixed build 6.1.7601.27067 KB5036969 (Monthly Rollup) — fixed build 6.2.9200.24821 KB5036960 (Monthly Rollup) — fixed build 6.3.9600.21924
🔗 References (29)
- advisoryhttps://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-26214
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036896
- referencehttps://support.microsoft.com/help/5036896
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036909
- referencehttps://support.microsoft.com/help/5036909
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036894
- referencehttps://support.microsoft.com/help/5036894
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036892
- referencehttps://support.microsoft.com/help/5036892
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036893
- referencehttps://support.microsoft.com/help/5036893
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036910
- referencehttps://support.microsoft.com/help/5036910
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036925
- referencehttps://support.microsoft.com/help/5036925
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036899
- referencehttps://support.microsoft.com/help/5036899
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036932
- referencehttps://support.microsoft.com/help/5036932
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036950
- referencehttps://support.microsoft.com/help/5036950
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036967
- referencehttps://support.microsoft.com/help/5036967
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036922
- referencehttps://support.microsoft.com/help/5036922
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036969
- referencehttps://support.microsoft.com/help/5036969
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036960
- referencehttps://support.microsoft.com/help/5036960