snowflake-connector-python@2.2.1 vulnerabilities
Snowflake Connector for Python
-
latest version
3.12.3
-
latest non vulnerable version
-
first published
7 years ago
-
latest version published
a month ago
-
licenses detected
- [0,)
Direct Vulnerabilities
Known vulnerabilities in the snowflake-connector-python package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
snowflake-connector-python is a Snowflake Connector for Python Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File due to the logging of sensitive information when the logging level is set to Note: If the SecretDetector logging formatter is enabled, could lead to incomplete JWT tokens and certain private key formats. How to fix Insertion of Sensitive Information into Log File? Upgrade |
[,3.12.3)
|
snowflake-connector-python is a Snowflake Connector for Python Affected versions of this package are vulnerable to Arbitrary 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. Mitigation: This attack scenario can be mitigated through URL whitelisting as well as common anti-phishing resources. How to fix Arbitrary Command Injection? Upgrade |
[,3.0.2)
|
snowflake-connector-python is a Snowflake Connector for Python Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) due to the usage of insecure regex. Exploiting this vulnerability is possible when an attacker can supply arbitrary input to the How to fix Regular Expression Denial of Service (ReDoS)? Upgrade |
[0,2.8.2)
|