First published: Thu Apr 10 2025(Updated: )
Metabase is an open source Business Intelligence and Embedded Analytics tool. When admins change Snowflake connection details in Metabase (either updating a password or changing password to private key or vice versa), Metabase would not always purge older Snowflake connection details from the application database. In order to remove older and stale connection details, Metabase would try one connection method at a time and purge all the other connection methods from the application database. When Metabase found a connection that worked, it would log (log/infof "Successfully connected, migrating to: %s" (pr-str test-details)) which would then print the username and password to the logger. This is fixed in 52.17.1, 53.9.5 and 54.1.5 in both the OSS and enterprise editions. Versions 51 and lower are not impacted.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Metabase | >51>=52.17.1<=54.1.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-32382 is classified as a medium severity vulnerability.
To fix CVE-2025-32382, ensure all Snowflake connection details are purged before updating or changing them in Metabase.
CVE-2025-32382 may lead to exposure of sensitive Snowflake connection details if older details are not properly purged.
CVE-2025-32382 affects Metabase versions from 51 to 54.1.5, excluding version 52.17.1.
Admins of Metabase using the affected versions who manipulate Snowflake connection details are vulnerable to CVE-2025-32382.