Skip to content

← Public intelligence

NuGet package

microsoft.data.sqlclient

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.7NuGetPublished

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

    CVE-2024-0056 · GHSA-98g6-xh36-x2p7

    Affected
    • NuGet microsoft.data.sqlclient < 2.1.7; >= 3.0.0, < 3.1.5; >= 4.0.0, < 4.0.5; >= 5.0.0, < 5.1.3
    Fixed in
    3.1.55.1.32.1.74.0.5· Vendor fix available
    Issue
    Microsoft.Data.SqlClient and System.Data.SqlClient SQL Data Provider Security Feature Bypass Vulnerability

    Recommended action: Upgrade to 5.1.3, 4.0.5, 3.1.5 or 2.1.7 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 5.8NuGetPublished

    .NET Information Disclosure Vulnerability

    CVE-2022-41064 · GHSA-8g2p-5pqh-5jmc

    Affected
    • NuGet microsoft.data.sqlclient <= 1.1.3; >= 2.0.0, < 2.1.2
    Fixed in
    1.1.42.1.2· Vendor fix available
    Issue
    Microsoft is releasing this security advisory to provide information about a vulnerability in .NET, .NET Core and .NET Framework's System.Data.SqlClient and Microsoft.Data.SqlClient NuGet Packages. A vulnerability exists in System.Data.SqlClient and Microsoft.Data.SqlClient libraries where a timeout occurring under high load can cause incorrect data to be returned as the result of an asynchronously executed query. <a name="mitigation-factors"</aMitigation factors If you are not talking to Microsoft SQL Server from your application you are not affected by this vulnerability. <a name="how-affected"</aHow do I know if I am affected? .NET has two types of dependencies: direct and transitive. Direct dependencies are dependencies where you specifically add a package to your project, transitive dependencies occur when you add a package to your project that in turn relies on another package. For example, the Microsoft.AspNetCore.Mvc package depends on the Microsoft.AspNetCore.Mvc.Core…

    Recommended action: Upgrade to 2.1.2 or 1.1.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →