CVE-2024-43382: Snowflake jdbc Snowflake JDBC Security Advisory Vulnerability

MODERATE
Advisory Identifier: GHSA-f686-hw9c-xw9c
CVSS 5.9
CWE-311 CWE-326
Published
Advisory Summary

CVE-2024-43382 is a MODERATE (CVSS 5.9) snowflake jdbc security advisory vulnerability (CWE-311: Missing Encryption of Sensitive Data) affecting Snowflake jdbc libraries in the Maven ecosystem. The issue involves snowflake jdbc security advisory. Remediation is available by upgrading affected packages to version 3.20.0.

CVE-2024-43382 at a Glance

CVE Identifier CVE-2024-43382
GHSA Identifier GHSA-f686-hw9c-xw9c
Severity MODERATE
CVSS v3.1 Base Score 5.9
CWE Classification CWE-311: Missing Encryption of Sensitive Data
Affected Product Snowflake jdbc
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2024-43382

To remediate this vulnerability, upgrade all affected Snowflake jdbc dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

net.snowflake:snowflake-jdbc fixed: 3.20.0
<dependency>
    <groupId>net.snowflake</groupId>
    <artifactId>snowflake-jdbc</artifactId>
    <version>3.20.0</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=net.snowflake

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2024-43382, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=net.snowflake

Analyze the terminal output to locate any version of Snowflake jdbc in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.20.0), your application is affected.

Note: The mvn dependency:tree -Dincludes=net.snowflake command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-311: Missing Encryption of Sensitive Data, where the product does not encrypt sensitive or critical information before storage or transmission. In Snowflake jdbc, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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](https://hackerone.com/snowflake?type=team).

CVE-2024-43382 Affected Snowflake jdbc Versions

1 component(s)
Fixed Versions:
3.20.0
Product / Package Ecosystem Affected Versions Fixed Version
net.snowflake:snowflake-jdbc
Maven
≥ 3.2.6
< 3.20.0
3.20.0

References

Frequently Asked Questions

What is CVE-2024-43382?
CVE-2024-43382 is a security vulnerability in Snowflake jdbc involving Snowflake JDBC Security Advisory under CWE-311: Missing Encryption of Sensitive Data.
Which Snowflake jdbc versions are affected?
Affected versions include releases prior to 3.20.0 across affected packages: net.snowflake:snowflake-jdbc.
What version fixes CVE-2024-43382?
Upgrading to 3.20.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is snowflake-jdbc affected?
Yes, net.snowflake:snowflake-jdbc is affected in releases prior to 3.20.0. Upgrade your dependency to 3.20.0 or later.
What is the CVSS score of CVE-2024-43382?
CVE-2024-43382 has a CVSS v3.1 base score of 5.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2024-43382?
CVE-2024-43382 is classified under CWE-311: Missing Encryption of Sensitive Data (The product does not encrypt sensitive or critical information before storage or transmission.).
How can I check Maven dependencies for CVE-2024-43382?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=net.snowflake'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-f686-hw9c-xw9c",
  "modified" : "2024-10-31T19:36:18Z",
  "published" : "2024-10-30T14:37:53Z",
  "aliases" : [ "CVE-2024-43382" ],
  "summary" : "Snowflake JDBC Security Advisory",
  "details" : "### Impacted Products\nSnowflake JDBC driver versions >= 3.2.6 & <= 3.19.1 are affected.\n\n### Introduction\nSnowflake 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.\n\n### Incorrect Security Setting Vulnerability \n#### Description\nSnowflake 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. \n#### Scenarios and attack vector(s)\nUsers 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. \n#### Our response\nOn 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. \n#### Resolution\nWe strongly recommend users to upgrade to 3.20.0 or later versions as soon as possible. \n\n### Contact\nIf 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](https://hackerone.com/snowflake?type=team).\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "net.snowflake:snowflake-jdbc"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.2.6"
      }, {
        "fixed" : "3.20.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.19.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/snowflakedb/snowflake-jdbc/security/advisories/GHSA-f686-hw9c-xw9c"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-43382"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/snowflakedb/snowflake-jdbc"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-311", "CWE-326" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-10-30T14:37:53Z",
    "nvd_published_at" : "2024-10-30T21:15:14Z"
  }
}