CVE-2023-34233

HighCVSS 8.8

Published: 08/06/2023(UTC)Updated: 17/06/2026(UTC)Translated: 18/06/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

High risk

1.84%

76th percentile - higher than 76% of all known CVEs

Summary

The Snowflake Connector for Python in versions prior to 3.0.2 is vulnerable to command injection via SSO browser URL authentication. An attacker can exploit a malicious resource to redirect users to a malicious URL, potentially leading to remote code execution.

Risk Assessment

Organizations may be exposed to remote code execution, which can result in data loss or system takeover. Exploitation of this vulnerability can have serious security implications for applications.

Recommendation

It is recommended to upgrade to version 3.0.2, which contains a patch for this vulnerability. Additionally, implementing URL whitelisting and utilizing anti-phishing resources is advisable.

Other vulnerabilities in Snowflake Connector for Python

CVE-2026-15925Critical
Snowflake Connector for Python versions prior to 4.7.1 and 3.18.1 lack proper TLS hostname verification. An attacker with on-path network access could intercept or redirect HTTPS traffic and present a certificate signed by any trusted CA for any domain, causing the connector to accept connections without validating the certificate matches the requested hostname.

Original NVD description (English source)

The Snowflake Connector for Python provides an interface for developing Python applications that can connect to Snowflake and perform all standard operations. Versions prior to 3.0.2 are vulnerable to command injection 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. Version 3.0.2 contains a patch for this issue.