MediumGHSA-hwcc-4cv8-cf3hCVE-2023-51662

Snowflake Connector .NET does not properly check the Certificate Revocation List (CRL)

Published 22 Dec 2023 · Updated 16 Feb 2024

Is your project on an affected Snowflake.Data?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
>=2.0.25 <2.1.5
Fixed in
2.1.5
Update to the fixed version for your release line, for example:dotnet add package Snowflake.Data --version 2.1.5

Details

Issue

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.

Attack Scenario

Snowflake uses CRL to check if a TLS certificate has been revoked before its expiration date. The lack of correct validation of revoked certificates could, in theory, allow an attacker who has both access to the private key of a correctly issued Snowflake certificate and the ability to intercept network traffic to perform a Man-in-the-Middle (MitM) attack in order to compromise Snowflake credentials used by the driver.

The vulnerability is difficult to exploit given both conditions required and, at the time of this advisory's publication, Snowflake is not aware of any compromise of its certificates, nor unauthorized issuance of such by any publicly trusted Certificate Authority (CA). However, an upgrade to the newest version is recommended to ensure the highest level of security and protection against future unforeseen threats.

Solution

On December 18, 2023, Snowflake released version 2.1.5 of the Snowflake Connector .NET, which fixes the issue, and we recommend users upgrade to version 2.1.5. Customers continuing to use the impacted versions of the connector should update their insecureMode flag to true.

Acknowledgement

Snowflake would like to thank Timo Vink for reporting this vulnerability.

Additional Information

If you discover a security vulnerability in one of our products or websites, please report the issue to HackerOne. For more information, please see our Vulnerability Disclosure Policy.

Is GHSA-hwcc-4cv8-cf3h in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected Snowflake.Data, and gives you the command that fixes it.

More advisories for Snowflake.Data

  • LowCVE-2025-46326Snowflake Connector for .NET has race condition when checking access to Easy Logging configuration file · 28 Apr 2025
  • MediumCVE-2025-24788Snowflake.Data has weak temporary files permissions · 29 Jan 2025
  • HighCVE-2023-34230Snowflake Connector .Net Command Injection · 9 Jun 2023
Snowflake.Data security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.