dbcve.org
Snowflake JdbcApplication · Snowflake

CVE-2024-43382

MEDIUM · 5.9 CVSS v3.1 Published 2024-10-30
Fix available
A fix is available. Upgrade to 3.20.0 or later.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Snowflake JDBC driver versions >= 3.2.6 and <= 3.19.1 have an Incorrect Security Setting that can result in data being uploaded to an encrypted stage without the additional layer of protection provided by client side encryption.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Snowflake JDBC driver versions 3.2.6 through 3.19.1 contain an incorrect security setting that causes client-side encryption to be bypassed when uploading data to encrypted stages. This means data may be stored with only server-side encryption rather than the intended additional layer of client-side protection.

MitigationUpgrade the Snowflake JDBC driver to version 3.19.2 or later to resolve the incorrect security setting. After upgrading, verify that client-side encryption is functioning as expected for uploads to encrypted stages.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Snowflake JdbcApplication
Affected:>= 3.2.6, < 3.20.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Snowflake JDBC driver version
    Check the JAR file name (e.g., snowflake-jdbc-3.x.x.jar) in your project dependencies (Maven pom.xml, Gradle build.gradle, or locate the JAR file in your lib/classpath directory). Alternatively, run: jar tf snowflake-jdbc.jar | grep 'META-INF/MANIFEST.MF' and inspect the Manifest file for the Implementation-Version attribute.
    Affected if The installed version is 3.2.6 through 3.19.1 (any version >= 3.2.6 and < 3.20.0)
  2. Verify if your application uploads data to encrypted Snowflake stages
    Review your application code for PUT commands or Stage API calls that upload files to Snowflake. Check your Snowflake stage definitions using: SHOW STAGES; or DESCRIBE STAGE <stage_name>; Look for STAGE_TYPE = 'S3'/'Azure'/'GCS' with ENCRYPTION = true, or internal stages with ENCRYPTION = true.
    Affected if Your application uploads data to any Snowflake stage that has encryption enabled (the flaw only affects uploads to encrypted stages)
  3. Confirm client-side encryption is expected but not applied
    Examine your data loading workflow to determine if client-side encryption was intended. Check the PUT command or stage configuration for CLIENT_STAGE_CSE_KEY or similar client-side encryption parameters. If client-side encryption is required but the driver bypasses it, data will only have server-side encryption.
    Affected if You expect client-side encryption for uploads but the driver is applying only server-side encryption due to the flawed security setting

You are affected if you use Snowflake JDBC driver version 3.2.6 through 3.19.1 AND upload data to encrypted stages while expecting client-side encryption protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.20.0 or later
Fixed in 3.20.0
Interim mitigation

Upgrade the Snowflake JDBC driver to version 3.19.2 or later to resolve the incorrect security setting. After upgrading, verify that client-side encryption is functioning as expected for uploads to encrypted stages.

Recommended fix High confidence

3.20.0 or later

  1. Update the Snowflake JDBC driver dependency in your project to version 3.20.0 or later
  2. For Maven projects, update the pom.xml dependency version to 3.20.0 or later
  3. For Gradle projects, update the build.gradle dependency version to 3.20.0 or later
  4. Rebuild and redeploy your application to apply the updated driver

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Snowflake Jdbc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43382 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43382 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data