Skip to content

Snowflake JDBC vulnerable to command injection via SSO URL authentication

High severity GitHub Reviewed Published Apr 13, 2023 in snowflakedb/snowflake-jdbc • Updated Apr 24, 2023

Package

maven net.snowflake:snowflake-jdbc (Maven)

Affected versions

< 3.13.29

Patched versions

3.13.29

Description

Snowflake JDBC driver is vulnerable to command injection vulnerability via SSO URL authentication. The vulnerability was patched on March 17, 2023 as part of Snowflake JDBC driver Version 3.13.29. An 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.

References

@sfc-gh-jfan sfc-gh-jfan published to snowflakedb/snowflake-jdbc Apr 13, 2023
Published to the GitHub Advisory Database Apr 14, 2023
Reviewed Apr 14, 2023
Published by the National Vulnerability Database Apr 14, 2023
Last updated Apr 24, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

EPSS score

0.754%
(82nd percentile)

CVE ID

CVE-2023-30535

GHSA ID

GHSA-4g3j-c4wg-6j7x
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.