Loss of client-side encryption via key-size misvalidation
Published Oct 30, 2024 · Updated Oct 31, 2024
Incorrect security setting in Snowflake JDBC Driver 3.2.6 through 3.19.1 causes encrypted-stage uploads to omit client-side encryption. Azure and GCP file-transfer clients apply an incorrect encryption-key-size condition when CLIENT_ENCRYPTION_KEY_SIZE is set to 256 bits. Only non-AWS accounts using the non-default 256-bit setting are exposed; TLS in transit and server-side encryption at rest remain intact.
Summary
What happened
Incorrect security setting in Snowflake JDBC Driver 3.2.6 through 3.19.1 causes encrypted-stage uploads to omit client-side encryption. Azure and GCP file-transfer clients apply an incorrect encryption-key-size condition when CLIENT_ENCRYPTION_KEY_SIZE is set to 256 bits. Only non-AWS accounts using the non-default 256-bit setting are exposed; TLS in transit and server-side encryption at rest remain intact.
The record
- CVE
- CVE-2024-43382
- Published
- Oct 30, 2024
- Updated
- Oct 31, 2024
- Vendor
- Snowflake
- Product
- Snowflake JDBC Driver
- Classifications
- CWE-311, CWE-326
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Oct 30, 2024CVE publishedPublication date reported by the CVE source.
- Oct 31, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.2.6 <=3.19.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo