Snowflake JDBC uses insecure temporary credential cache file permissionsGHSA-33g6-495w-v8j2
MEDIUMFix: snowflakedb/snowflake-jdbc@9e1a5acGHSA-33g6-495w-v8j2 is a medium-severity (CVSS 4.4) Incorrect Default Permissions vulnerability in net.snowflake:snowflake-jdbc. A fix is available for net.snowflake:snowflake-jdbc — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-33g6-495w-v8j2.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
net.snowflake:snowflake-jdbcReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Issue
Snowflake discovered and remediated a vulnerability in the Snowflake JDBC Driver. On Linux systems, when temporary credential caching is enabled, the Snowflake JDBC Driver will cache temporary credentials locally in a world-readable file.
This vulnerability affects versions 3.6.8 through 3.21.0. Snowflake fixed the issue in version 3.22.0.
Vulnerability Details
On Linux, when either EXTERNALBROWSER or USERNAME_PASSWORD_MFA authentication methods are used with temporary credential caching enabled, the Snowflake JDBC Driver will cache temporary credentials in a local file. In the vulnerable versions of the Driver, this file is created with world-readable permissions.
Solution
Snowflake released version 3.22.0 of the Snowflake JDBC Driver, which fixes this issue. We recommend users upgrade to version 3.22.0.
Additional Information
If you discover a security vulnerability in one of our products or websites, please report the issue to HackerOne. For more information, please see our Vulnerability Disclosure Policy.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | net.snowflake:snowflake-jdbc | ≥ 3.6.8&&< 3.22.0 | 3.22.0net.snowflake:snowflake-jdbc:3.22.0 |
Affected Products
snowflake jdbcsnowflakeDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.snowflake:snowflake-jdbc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update net.snowflake:snowflake-jdbc to 3.22.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-33g6-495w-v8j2 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is GHSA-33g6-495w-v8j2 in your dependencies?
Find it across Maven, including transitive dependencies.