Snowflake Connector .NET does not properly check the Certificate Revocation List (CRL)
CVE-2023-51662GHSA-hwcc-4cv8-cf3h
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (snowflake.data 2.1.5), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
NuGet snowflake.data
- Affected
- >= 2.0.25, <= 2.1.4
- Fixed in
- 2.1.5
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-hwcc-4cv8-cf3h lists affected ranges: NuGet snowflake.data >=2.0.25 <=2.1.4
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.0 · CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:L
- EPSS
- CVE-2023-51662: 0.35% estimated exploitation activity in the next 30 days; percentile 28.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-hwcc-4cv8-cf3h
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2023-51662 Advisory: Snowflake Connector .NET does not properly check the Certificate Revocation List (CRL) IDs: CVE-2023-51662, GHSA-hwcc-4cv8-cf3h Record: https://patchnext.com/advisories/cve-2023-51662 (revision 1, source checked 26 Oct 2026, 17:00 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.0) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: snowflake.data 2.1.5. A vendor fix does not mean a deployment is fixed. ## Affected components - NuGet snowflake.data: affected >= 2.0.25, <= 2.1.4; fixed in 2.1.5 ## Suggested inspection (read-only) - NuGet snowflake.data: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on snowflake.data. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-hwcc-4cv8-cf3h (GitHub-reviewed advisory GHSA-hwcc-4cv8-cf3h lists affected ranges: NuGet snowflake.data >=2.0.25 <=2.1.4) Commands are suggestions: review each one before running it.
Loading voting…