Approved changes feed: RSS · Atom

cpe:2.3:a:snowflake:gosnowflake:*:*:*:*:*:go:*:*

part: a version: * update: *

VendorSnowflake (de799455-6744-506b-babc-9114bb379007)
ProductGosnowflake (c8051b83-d218-589e-839f-214465f09357)
Edition*
Language*
Software edition*
Target softwarego
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2025-46327 vulnerable 2026-06-08 07:27:08.056817 Go Snowflake Driver has race condition when checking access to Easy Logging configuration file
LOW (3.3)
gosnowflake is the Snowflake Golang driver. Versions starting from 1.7.0 to before 1.13.3, are vulnerable to a Time-of-Check to Time-of-Use (TOCTOU) race condition. When using the Easy Logging feature on Linux and macOS, the Driver reads logging configuration from a user-provided file. On Linux and macOS the Driver verifies that the configuration file can be written to only by its owner. That check was vulnerable to a TOCTOU race condition and failed to verify that the file owner matches the user running the Driver. 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. This issue has been patched in version 1.13.3.
Published: 2025-04-28T22:33:05.249Z
Updated: 2025-04-29T13:43:12.167Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-34231 vulnerable 2026-06-08 06:06:24.907487 Snowflake Golang Driver vulnerable to Command Injection
HIGH (7.3)
gosnowflake is th Snowflake Golang driver. Prior to version 1.6.19, a command injection vulnerability exists in the Snowflake Golang driver via single sign-on (SSO) browser URL authentication. In order to exploit the potential for command injection, an attacker would need to be successful in (1) establishing a malicious resource and (2) redirecting users to utilize the resource. The attacker could set up a malicious, publicly accessible server which responds to the SSO URL with an attack payload. If the attacker then tricked a user into visiting the maliciously crafted connection URL, the user’s local machine would render the malicious payload, leading to a remote code execution. This attack scenario can be mitigated through URL whitelisting as well as common anti-phishing resources. A patch is available in version 1.6.19.
Published: 2023-06-08T19:42:13.381Z
Updated: 2025-01-06T19:45:43.259Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.