NVD / CVE Program· CNA mitre

CVE-2024-43382: 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 encryp

Noroxi assessment

Priority: Monitor (action score 23/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: net.snowflake:snowflake-jdbc (Maven) 3.20.0.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to net.snowflake:snowflake-jdbc (Maven) 3.20.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.9 · v3.1—No exploit Fix available

Weak crypto

GHSA-f686-hw9c-xw9c

Published: Oct 30, 2024
Updated: Jun 17, 2026
EPSS: 0.1% · 7th percentile
CWE: CWE-326

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 23 / 40 · 5.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
snowflake	snowflake jdbc	cpe:2.3:a:snowflake:snowflake_jdbc

Check your site's encryption

This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

snowflake snowflake jdbc3.2.6 and later · before 3.20.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Maven	net.snowflake:snowflake-jdbc	from 3.2.6 · before 3.20.0	3.20.0

Same product

snowflake: all records

Other highest-scoring records for the same primary product.

CVE-2023-30535Snowflake JDBC vulnerable to command injection via SSO URL authentication
36Monitor
CVE-2025-24789Snowflake JDBC allows an untrusted search path on Windows
31Monitor
CVE-2025-24790Snowflake JDBC uses insecure temporary credential cache file permissions
22Monitor

Published before and after this one in the same product

Later →CVE-2025-27496Mar 13, 2025 · Snowflake JDBC Driver client-side encryption key in DEBUG logs
13Monitor
Later →CVE-2026-3293Feb 27, 2026 · snowflakedb snowflake-jdbc JDBC URL SdkProxyRoutePlanner.java SdkProxyRoutePlanner redos
7Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Maven:net.snowflake:snowflake-jdbc	3.20.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).