Metabase up to 52.17.1/53.9.5/54.1.5 log file

Summaryinfo

A vulnerability categorized as problematic has been discovered in Metabase up to 52.17.1/53.9.5/54.1.5. This issue affects some unknown processing. Executing a manipulation can lead to log file. This vulnerability is handled as CVE-2025-32382. The attack can be executed remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Metabase up to 52.17.1/53.9.5/54.1.5. It has been declared as problematic. This vulnerability affects an unknown functionality. The manipulation with an unknown input leads to a log file vulnerability. The CWE definition for the vulnerability is CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. As an impact it is known to affect confidentiality. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability was named CVE-2025-32382 since 04/06/2025. The exploitation appears to be easy. The attack can be initiated remotely. The exploitation needs additional levels of successful authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.

Upgrading to version 0.52.17.1, 0.53.9.5, 0.54.1.5, 1.52.17.1, 1.53.9.5 or 1.54.1.5 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Metabase

Version

• 52.17.0
• 52.17.1
• 53.9.0
• 53.9.1
• 53.9.2
• 53.9.3
• 53.9.4
• 53.9.5
• 54.1.0
• 54.1.1
• 54.1.2
• 54.1.3
• 54.1.4
• 54.1.5

Website

• Product: https://github.com/metabase/metabase/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion