CVE-2024-43382: Snowflake JDBC Security Advisory
Impacted Products Snowflake JDBC driver versions = 3.2.6 & <= 3.19.1 are affected. Introduction Snowflake recently identified an issue affecting JDBC drivers that can result in data being uploaded to an encrypted stage without the additional layer of protection provided by client side encryption.
Published Oct 30, 2024 · Updated Oct 31, 2024
Affected packages
net.snowflake:snowflake-jdbc
- Ecosystem
- Maven
- Affected
- >= 3.2.6, <= 3.19.1
- Fixed in
- 3.20.0
- Check
mvn dependency:tree -Dincludes=net.snowflake:snowflake-jdbc
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impacted Products
Snowflake JDBC driver versions >= 3.2.6 & <= 3.19.1 are affected.
Introduction
Snowflake recently identified an issue affecting JDBC drivers that can result in data being uploaded to an encrypted stage without the additional layer of protection provided by client side encryption. The issue, which affects only a subset of accounts hosted on Azure and GCP deployments (AWS deployments are not affected), manifests in instances where customers create a stage using a JDBC driver with the CLIENT_ENCRYPTION_KEY_SIZE account parameter set to 256-bit rather than the default 128-bit. The data is still protected by TLS in transit and server side encryption at rest. This missed layer of the additional protection is not visible to the affected customers.
Incorrect Security Setting Vulnerability
Description
Snowflake identified an incorrect security setting in Snowflake JDBC drivers. Snowflake has evaluated the severity of the issue and determined it was in medium range with a maximum CVSSv3 base score of 5.9.
Scenarios and attack vector(s)
Users of Snowflake JDBC drivers with accounts on Azure and GCP deployments who set the parameter CLIENT_ENCRYPTION_KEY_SIZE = 256 were subject to this incorrect security setting vulnerability as it could result in data being uploaded to a stage without an additional layer for encryption.
Our response
On July 23, 2024, Snowflake discovered this vulnerability. On 10/28/2024, Snowflake released a patch in Snowflake JDBC driver Version 3.20.0. The patch fixes the incorrect security setting.
Resolution
We strongly recommend users to upgrade to 3.20.0 or later versions as soon as possible.
Contact
If you discover a security vulnerability in one of our products or websites, please report the issue to HackerOne. For more information, please see our Vulnerability Disclosure Policy.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Maven vulnerabilities
All Maven entriesCVE-2026-86597
Snowflake drivers writes sensitive information to logs
medium6.5No fixOct 5, 2026CVE-2026-3293
Snowflake JDBC Driver is Vulnerable to Uncontrolled Resource Consumption through SdkProxyRoutePlanner
low3.3No fixFeb 27, 2026CVE-2025-27496
Snowflake JDBC Driver client-side encryption key in DEBUG logs
low3.3Mar 13, 2025CVE-2025-24789
Snowflake JDBC allows an untrusted search path on Windows
high7.8Jan 29, 2025CVE-2025-24790
Snowflake JDBC uses insecure temporary credential cache file permissions
medium4.4Jan 29, 2025
