NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
HIGH severity

CVE-2024-0056 — Microsoft.Data.SqlClient

HIGH

CVE-2024-0056 is a high-severity (CVSS 8.7) CWE-319 vulnerability in Microsoft.Data.SqlClient. A fix is available for Microsoft.Data.SqlClient — see the affected versions and patch details below.

Microsoft.Data.SqlClient and System.Data.SqlClient vulnerable to SQL Data Provider Security Feature Bypass

Also known asBIT-dotnet-2024-0056BIT-dotnet-sdk-2024-0056GHSA-98g6-xh36-x2p7
Published
Updated
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-0056.

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk
0.67%1.01%1.34%1.68%1.2%1.2%1.2%1.2%1.2%Jul 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected
.NETMicrosoft.Data.SqlClient.NETSystem.Data.SqlClient.NETMicrosoft.Data.SqlClient.NETMicrosoft.Data.SqlClient.NETMicrosoft.Data.SqlClient

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Microsoft.Data.SqlClient and System.Data.SqlClient SQL Data Provider Security Feature Bypass Vulnerability

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.Data.SqlClientall versions2.1.7dotnet add package Microsoft.Data.SqlClient --version 2.1.7
.NETNuGetSystem.Data.SqlClientall versions4.8.6dotnet add package System.Data.SqlClient --version 4.8.6
.NETNuGetMicrosoft.Data.SqlClient≥ 3.0.0&&< 3.1.53.1.5dotnet add package Microsoft.Data.SqlClient --version 3.1.5
.NETNuGetMicrosoft.Data.SqlClient≥ 4.0.0&&< 4.0.54.0.5dotnet add package Microsoft.Data.SqlClient --version 4.0.5
.NETNuGetMicrosoft.Data.SqlClient≥ 5.0.0&&< 5.1.35.1.3dotnet add package Microsoft.Data.SqlClient --version 5.1.3

Affected Products

6 products · 27 configurations
Application
.netmicrosoft
≥ 7.0.0 && < 7.0.15
1 version
8.0.0
Application
.net frameworkmicrosoft
≥ 4.8 && < 4.8.04690.02
7 versions
2.03.54.6.24.74.7.14.7.24.8.1
Application
microsoft.data.sqlclientmicrosoft
≥ 5.1 && < 5.1.3
range
Application
sql servermicrosoft
1 version
2022
Application
system.data.sqlclientmicrosoft
< 4.8.6
range
Application
visual studio 2022microsoft
≥ 17.8 && < 17.8.4
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.Data.SqlClient, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update Microsoft.Data.SqlClient to 2.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-0056 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This flaw allows attackers to execute an adversary-in-the-middle (AiTM) attack, potentially enabling the theft of authentication credentials even when the connection is encrypted with protocols like TLS. This security lapse could lead to unauthorized access to sensitive databases, raising concerns about data breaches…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2024-0056 (CC BY 4.0)
ProductFixed inAdvisory
.NET Core on Red Hat Enterprise Linuxrh-dotnet60-dotnet-0:6.0.126-1.el7_9RHSA-2024:0255
Red Hat Enterprise Linux 8dotnet8.0-0:8.0.101-1.el8_9RHSA-2024:0150
Red Hat Enterprise Linux 8dotnet7.0-0:7.0.115-1.el8_9RHSA-2024:0157
Red Hat Enterprise Linux 8dotnet6.0-0:6.0.126-1.el8_9RHSA-2024:0158
Red Hat Enterprise Linux 9dotnet7.0-0:7.0.115-1.el9_3RHSA-2024:0151
Red Hat Enterprise Linux 9dotnet8.0-0:8.0.101-1.el9_3RHSA-2024:0152
Red Hat Enterprise Linux 9dotnet6.0-0:6.0.126-1.el9_3RHSA-2024:0156

Frequently Asked Questions

Microsoft.Data.SqlClient and System.Data.SqlClient SQL Data Provider Security Feature Bypass Vulnerability
O3 Security · Impact-Aware SCA

Is CVE-2024-0056 in your dependencies?

Find it across NuGet, including transitive dependencies.

CVE-2024-0056: Microsoft.Data.SqlClient — Fixed in 2.1.7