CVE-2025-32382

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.

CVSS

No CVSS.

References

Link	Resource
https://github.com/metabase/metabase/security/advisories/GHSA-832j-56xw-5p7f

Configurations

No configuration.

History

11 Apr 2025, 15:39

Type	Values Removed	Values Added
Summary		(es) Metabase es una herramienta de inteligencia empresarial y análisis integrado de código abierto. Cuando los administradores cambian los detalles de conexión de Snowflake en Metabase (ya sea actualizando una contraseña o cambiando la contraseña a una clave privada o viceversa), Metabase no siempre purga los detalles de conexión de Snowflake más antiguos de la base de datos de la aplicación. Para eliminar detalles de conexión más antiguos y obsoletos, Metabase probaría un método de conexión a la vez y purgaría todos los demás métodos de conexión de la base de datos de la aplicación. Cuando Metabase encontraba una conexión que funcionaba, registraba (log/infof "Conectado exitosamente, migrando a: %s" (pr-str test-details)) que luego imprimía el nombre de usuario y la contraseña en el registrador. Este problema se ha solucionado en 52.17.1, 53.9.5 y 54.1.5 tanto en la edición OSS como en la empresarial. Las versiones 51 y anteriores no se ven afectadas.

10 Apr 2025, 15:16

Type	Values Removed	Values Added
New CVE

Information

Published : 2025-04-10 15:16

Updated : 2025-04-11 15:39

NVD link : CVE-2025-32382

Mitre link : CVE-2025-32382

CVE.ORG link : CVE-2025-32382

JSON object : View

Products Affected

No product.

CWE

CWE-532

Insertion of Sensitive Information into Log File

{"id": "CVE-2025-32382", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 1.8, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "LOW", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "ACTIVE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "HIGH", "subIntegrityImpact": "LOW", "vulnIntegrityImpact": "NONE", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "LOW", "vulnConfidentialityImpact": "NONE", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2025-04-10T15:16:05.560", "references": [{"url": "https://github.com/metabase/metabase/security/advisories/GHSA-832j-56xw-5p7f", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-532"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Metabase es una herramienta de inteligencia empresarial y an\u00e1lisis integrado de c\u00f3digo abierto. Cuando los administradores cambian los detalles de conexi\u00f3n de Snowflake en Metabase (ya sea actualizando una contrase\u00f1a o cambiando la contrase\u00f1a a una clave privada o viceversa), Metabase no siempre purga los detalles de conexi\u00f3n de Snowflake m\u00e1s antiguos de la base de datos de la aplicaci\u00f3n. Para eliminar detalles de conexi\u00f3n m\u00e1s antiguos y obsoletos, Metabase probar\u00eda un m\u00e9todo de conexi\u00f3n a la vez y purgar\u00eda todos los dem\u00e1s m\u00e9todos de conexi\u00f3n de la base de datos de la aplicaci\u00f3n. Cuando Metabase encontraba una conexi\u00f3n que funcionaba, registraba (log/infof \"Conectado exitosamente, migrando a: %s\" (pr-str test-details)) que luego imprim\u00eda el nombre de usuario y la contrase\u00f1a en el registrador. Este problema se ha solucionado en 52.17.1, 53.9.5 y 54.1.5 tanto en la edici\u00f3n OSS como en la empresarial. Las versiones 51 y anteriores no se ven afectadas."}], "lastModified": "2025-04-11T15:39:52.920", "sourceIdentifier": "security-advisories@github.com"}