You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Security information
Factors contributing to the scoring:
Snyk: [CVSS v4.0 7.4](https://security.snyk.io/vuln/SNYK-JAVA-NETSNOWFLAKE-8310506) - High Severity | [CVSS v3.1 5.9](https://security.snyk.io/vuln/SNYK-JAVA-NETSNOWFLAKE-8310506) - Medium Severity
NVD: Not available. NVD has not yet published its analysis.
Why are the scores different? Learn how Snyk evaluates vulnerability scores
Overview
Affected versions of this package are vulnerable to Missing Encryption of Sensitive Data due to a misbounded check in the createUploadStream() function for Azure and GCP systems. When the CLIENT_ENCRYPTION_KEY_SIZE of a stage using a JDBC driver is set to the non-default 256-bit size. An attacker can upload data which will be stored on the client side without encryption. It is still encrypted in transit and on the server.
Note: AWS deployments are not vulnerable.
The text was updated successfully, but these errors were encountered:
Introduced through
org.flywaydb:[email protected]
Fixed in
net.snowflake:[email protected]
Detailed paths
Security information
Factors contributing to the scoring:
Why are the scores different? Learn how Snyk evaluates vulnerability scores
Overview
Affected versions of this package are vulnerable to Missing Encryption of Sensitive Data due to a misbounded check in the createUploadStream() function for Azure and GCP systems. When the CLIENT_ENCRYPTION_KEY_SIZE of a stage using a JDBC driver is set to the non-default 256-bit size. An attacker can upload data which will be stored on the client side without encryption. It is still encrypted in transit and on the server.
Note: AWS deployments are not vulnerable.
The text was updated successfully, but these errors were encountered: