Description
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.
Problem types
CWE-532: Insertion of Sensitive Information into Log File
Product status
>= 1.52.12, < 1.52.17.1
>= 0.53.2.3, < 0.53.9.5
>= 1.53.2.3, < 1.53.9.5
>= 0.54.0.0, < 0.54.1.5
>= 1.54.0.0, < 1.54.1.5
References
github.com/...tabase/security/advisories/GHSA-832j-56xw-5p7f