Snowflake Connector for .NET has race condition when checking access to Easy Logging configuration file
Published 28 Apr 2025 · Updated 29 Apr 2025
Is your project on an affected Snowflake.Data?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=2.1.2 <4.4.1
- Fixed in
- 4.4.1
dotnet add package Snowflake.Data --version 4.4.1Details
Issue
Snowflake discovered and remediated a vulnerability in the Snowflake Connector for .NET (“Connector”). When using the Easy Logging feature on Linux and macOS, the Connector didn’t correctly verify the permissions of the logging configuration file, potentially allowing an attacker with local access to overwrite the configuration and gain control over logging level and output location.
This vulnerability affects Connector versions 2.1.2 through 4.4.0. Snowflake fixed the issue in version 4.4.1.
Vulnerability Details
When using the Easy Logging feature on Linux and macOS, the Connector reads logging configuration from a user-provided file. On Linux and macOS, the Connector verifies that the configuration file can be written to only by its owner. That check was vulnerable to a Time-of-Check to Time-of-Use (TOCTOU) race condition and failed to verify that the file owner matches the user running the Connector. This could allow a local attacker with write access to the configuration file or the directory containing it to overwrite the configuration and gain control over logging level and output location.
Solution
Snowflake released version 4.4.1 of the Snowflake Connector for .NET, which fixes this issue. We recommend users upgrade to version 4.4.1.
Additional Information
If you discover a security vulnerability in one of our products or websites, please report the issue to Snowflake through our Vulnerability Disclosure Program hosted at HackerOne. For more information, please see our Vulnerability Disclosure Policy.
Is GHSA-c82r-c9f7-f5mj 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
- MediumCVE-2025-24788Snowflake.Data has weak temporary files permissions · 29 Jan 2025
- MediumCVE-2023-51662Snowflake Connector .NET does not properly check the Certificate Revocation List (CRL) · 22 Dec 2023
- HighCVE-2023-34230Snowflake Connector .Net Command Injection · 9 Jun 2023
References
- Linkgithub.com/snowflakedb/snowflake-connector-net/security/advisories/GHSA-c82r-c9f7-f5mj
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-46326
- Linkgithub.com/snowflakedb/snowflake-connector-net/commit/393aad3cfa81045a05dd488944db45256e861bff
- Packagegithub.com/snowflakedb/snowflake-connector-net
- Linkgithub.com/snowflakedb/snowflake-connector-net/releases/tag/v4.4.1
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.