CVE-2024-0056: Microsoft.Data.SqlClient and System.Data.SqlClient SQL Data Provider Security Feature Bypass Vulnerability

Overview

Severity

High (CVSS 8.7)

CVSS Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N/E:U/RL:O/RC:C

Category

Security Feature Bypass

Exploit Status

Not Exploited

Exploitation Likelihood

Less Likely

Patch Tuesday

2024-Jan

Released

2024-01-09

Last Updated

2024-02-13

EPSS Score

0.86% (percentile: 75.1%)

FAQ

According to the CVSS metric, the attack complexity is high (AC:H). What does that mean for this vulnerability? The attacker must inject themselves into the logical network path between the target and the resource requested by the victim to read or modify network communications. This is called a machine-in-the-middle (MITM) attack. If I am using System.Data.SqlClient or Microsoft.Data.SqlClient, what do I need to do to be protected from this vulnerability? Customers developing applications using either the System.Data.SqlClient or Microsoft.Data.SqlClient NuGet Packages need to do the following to be protected: If you are using System.Data.SqlClient on .NET Framework you must install the January 2024 update(s) for .NET Framework If you are using System.Data.SqlClient on .NET 6, .NET 7, or .NET 8 you must update your NuGet package reference to an updated version as listed in the affected packages. If you are using Microsoft.Data.SqlClient, anywhere (.NET 6/7/8, .NET Framework) and you are using a version that is vulnerable you must update your NuGet package reference as listed in the affected packages. Please see Microsoft Security Advisory CVE 2024-0056 | .NET Information Disclosure Vulnerability. Please Note: Customers running applications that install either System.Data.SqlClient.dll or Microsoft.Data.SqlClient.dll should contact the application developer for application updates. According to the CVSS metric, a successful exploitation could lead to a scope change (S:C). What does this mean for this vulnerability? A successful attack could exploit a vulnerability in the SQL Data Provider which allows the attacker to exploit the SQL Server. How could an attacker exploit this vulnerability? An attacker who successfully exploited this vulnerability could carry out a machine-in-the-middle (MITM) attack and could decrypt and read or modify TLS traffic between the client and server. There is no impact to the availability of the attacked machine (A:N). What security fea

Affected Products (70)

SQL Server

• Microsoft SQL Server 2022 for x64-based Systems (GDR)
• Microsoft.Data.SqlClient 2.1
• Microsoft.Data.SqlClient 3.1
• Microsoft.Data.SqlClient 4.0
• Microsoft.Data.SqlClient 5.1
• System.Data.SqlClient
• Microsoft SQL Server 2022 for x64-based Systems (CU 10)

Developer Tools

• .NET 6.0
• .NET 7.0
• .NET 8.0
• Microsoft Visual Studio 2022 version 17.2
• Microsoft Visual Studio 2022 version 17.4
• Microsoft Visual Studio 2022 version 17.6
• Microsoft Visual Studio 2022 version 17.8
• Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for 32-bit Systems
• Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for x64-based Systems
• Microsoft .NET Framework 4.8 on Windows Server 2016 (Server Core installation)
• Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1
• Microsoft .NET Framework 4.8 on Windows Server 2016
• Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
• Microsoft .NET Framework 4.8 on Windows Server 2012 (Server Core installation)
• Microsoft .NET Framework 4.8 on Windows Server 2012
• Microsoft .NET Framework 4.8 on Windows Server 2012 R2
• Microsoft .NET Framework 4.8 on Windows Server 2012 R2 (Server Core installation)
• Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for 32-bit Systems
• Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for x64-based Systems
• Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019
• Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019 (Server Core installation)
• Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022
• Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022 (Server Core installation)
• Microsoft .NET Framework 3.5 AND 4.8 on Windows 11 version 21H2 for x64-based Systems
• Microsoft .NET Framework 3.5 AND 4.8 on Windows 11 version 21H2 for ARM64-based Systems
• Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 for 32-bit Systems
• Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 for ARM64-based Systems
• Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 for x64-based Systems
• Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 22H2 for x64-based Systems
• Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 22H2 for ARM64-based Systems
• Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 22H2 for 32-bit Systems
• Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for 32-bit Systems
• Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for x64-based Systems
• Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for ARM64-based Systems
• Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019
• Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019 (Server Core installation)
• Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1607 for 32-bit Systems
• Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2016
• Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1607 for x64-based Systems
• Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2016 (Server Core installation)
• Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2008 R2 for x64-based Systems Service Pack 1
• Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
• Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012
• Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 (Server Core installation)
• Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 R2 (Server Core installation)
• Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 R2
• Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2022 (Server Core installation)
• Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2022
• Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 21H2 for x64-based Systems
• Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 21H2 for ARM64-based Systems
• ... and 13 more

Security Updates (34)

• 5032968
• 5033733
• 5033734
• 5033741
• Release Notes
• Release Notes
• Release Notes
• Release Notes
• Release Notes
• Release Notes
• Release Notes
• Release Notes
• Release Notes
• 5033592
• 5033910
• 5034277
• 5034269
• 5034278
• 5034279
• 5034273
• 5034272
• 5034276
• 5034274
• 5034273
• 5034119
• 5034269
• 5034278
• 5034279
• 5034272
• 5034276
• ... and 4 more

Acknowledgments

Vishal Mishra and Anita Gaud with Microsoft's Azure DevSec Variant Hunt Team

Revision History

• 2024-01-09: Information published.
• 2024-01-12: Corrected Download and Article links in the Security Updates table. This is an informational change only.
• 2024-01-22: Corrected Download links in the Security Updates table. This is an informational change only.
• 2024-02-13: To address a known issue with a broken link, corrected Download links in the Security Updates table. This is an informational change only.