Snowflake JDBC driver up to 3.19.1 Setting missing encryption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Snowflake JDBC driver up to 3.19.1. This vulnerability affects unknown code of the component Setting Handler. This manipulation causes missing encryption. This vulnerability is handled as CVE-2024-43382. There is not any exploit available.
Details
A vulnerability was found in Snowflake JDBC driver up to 3.19.1. It has been declared as problematic. Affected by this vulnerability is some unknown functionality of the component Setting Handler. The manipulation with an unknown input leads to a missing encryption vulnerability. The CWE definition for the vulnerability is CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. As an impact it is known to affect confidentiality. The summary by CVE is:
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.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2024-43382 since 08/10/2024. The exploitation appears to be difficult. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.
The vulnerability scanner Nessus provides a plugin with the ID 214596 (Oracle Business Intelligence Publisher 7.0 / 7.6 (OAS) (January 2025 CPU)), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Tenable (214596). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.6VulDB Meta Temp Score: 2.6
VulDB Base Score: 2.6
VulDB Temp Score: 2.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Missing encryptionCWE: CWE-311 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 214596
Nessus Name: Oracle Business Intelligence Publisher 7.0 / 7.6 (OAS) (January 2025 CPU)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/10/2024 🔍10/31/2024 🔍
10/31/2024 🔍
08/20/2025 🔍
Sources
Advisory: GHSA-f686-hw9c-xw9cStatus: Confirmed
CVE: CVE-2024-43382 (🔍)
GCVE (CVE): GCVE-0-2024-43382
GCVE (VulDB): GCVE-100-282571
Entry
Created: 10/31/2024 08:55Updated: 08/20/2025 22:35
Changes: 10/31/2024 08:55 (55), 01/25/2025 00:09 (2), 08/20/2025 22:35 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.