dbcve.org
Snowflake ConnectorApplication · Snowflake

CVE-2023-51662

HIGH · 7.5 CVSS v3.1 Published 2023-12-22
Fix available
A fix is available. Upgrade to 2.1.5 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Snowflake .NET driver provides an interface to the Microsoft .NET open source software framework for developing applications. Snowflake recently received a report about a vulnerability in the Snowflake Connector .NET where the checks against the Certificate Revocation List (CRL) were not performed where the insecureMode flag was set to false, which is the default setting. The vulnerability affects versions between 2.0.25 and 2.1.4 (inclusive). Snowflake fixed the issue in version 2.1.5.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Snowflake Connector .NET fails to perform Certificate Revocation List (CRL) checks when insecureMode is set to false (the default), meaning revoked certificates are not validated during TLS connections. This could allow a man-in-the-middle attack using a revoked certificate to intercept encrypted communications between the application and Snowflake.

MitigationUpgrade the Snowflake Connector .NET to version 2.1.5 or later to enable proper CRL validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Snowflake ConnectorApplication
Affected:>= 2.0.25, < 2.1.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Find installed Snowflake Connector .NET version
    Inspect the installed package in your project dependencies or check the assembly version of Snowflake.Data.dll if deployed as a compiled application
    Affected if Version is 2.0.25 through 2.1.4 (inclusive)
  2. Verify affected version range
    Compare your installed version against the vulnerable range: versions >= 2.0.25 and < 2.1.5 are affected
    Affected if Your installed version falls within this range and you are using the Snowflake Connector .NET
  3. Check insecureMode configuration
    Inspect your connection string or application configuration files for the insecureMode parameter. This parameter controls whether certificate validation is bypassed during TLS connections to Snowflake
    Affected if insecureMode is set to false (the default) or is not explicitly set - this is the default vulnerable configuration

You are affected if you have Snowflake Connector .NET version 2.0.25 through 2.1.4 installed and your connection uses insecureMode=false (the default setting), as CRL validation is disabled in this configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.5 or later
Fixed in 2.1.5
Interim mitigation

Upgrade the Snowflake Connector .NET to version 2.1.5 or later to enable proper CRL validation.

Recommended fix High confidence

version 2.1.5 or later

  1. 1. Identify the current version of Snowflake Connector for .NET in your project (check .csproj file or NuGet package manager)
  2. 2. Update the Snowflake Connector package reference to version 2.1.5 or later
  3. 3. If using NuGet Package Manager Console, run: Update-Package Snowflake.Data or specify the version: Update-Package Snowflake.Data -Version 2.1.5
  4. 4. If editing .csproj directly, update the PackageReference to: <PackageReference Include="Snowflake.Data" Version="2.1.5" />
  5. 5. Rebuild the project to ensure the new package is properly installed
  6. 6. Verify the installed version matches 2.1.5 or later using NuGet package manager
Caveat standard minor version upgrade - review release notes for any behavior changes, though this is primarily a security fix

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Snowflake Connector Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51662 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-51662 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data