{"resultsPerPage":1,"startIndex":0,"totalResults":1,"format":"NVD_CVE","version":"2.0","timestamp":"2026-04-14T22:25:45.705","vulnerabilities":[{"cve":{"id":"CVE-2025-32382","sourceIdentifier":"security-advisories@github.com","published":"2025-04-10T15:16:05.560","lastModified":"2025-04-11T15:39:52.920","vulnStatus":"Awaiting Analysis","cveTags":[],"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á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."}],"metrics":{"cvssMetricV40":[{"source":"security-advisories@github.com","type":"Secondary","cvssData":{"version":"4.0","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","baseScore":1.8,"baseSeverity":"LOW","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"PRESENT","privilegesRequired":"HIGH","userInteraction":"ACTIVE","vulnConfidentialityImpact":"NONE","vulnIntegrityImpact":"NONE","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"LOW","subIntegrityImpact":"LOW","subAvailabilityImpact":"NONE","exploitMaturity":"NOT_DEFINED","confidentialityRequirement":"NOT_DEFINED","integrityRequirement":"NOT_DEFINED","availabilityRequirement":"NOT_DEFINED","modifiedAttackVector":"NOT_DEFINED","modifiedAttackComplexity":"NOT_DEFINED","modifiedAttackRequirements":"NOT_DEFINED","modifiedPrivilegesRequired":"NOT_DEFINED","modifiedUserInteraction":"NOT_DEFINED","modifiedVulnConfidentialityImpact":"NOT_DEFINED","modifiedVulnIntegrityImpact":"NOT_DEFINED","modifiedVulnAvailabilityImpact":"NOT_DEFINED","modifiedSubConfidentialityImpact":"NOT_DEFINED","modifiedSubIntegrityImpact":"NOT_DEFINED","modifiedSubAvailabilityImpact":"NOT_DEFINED","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}}]},"weaknesses":[{"source":"security-advisories@github.com","type":"Secondary","description":[{"lang":"en","value":"CWE-532"}]}],"references":[{"url":"https:\/\/github.com\/metabase\/metabase\/security\/advisories\/GHSA-832j-56xw-5p7f","source":"security-advisories@github.com"}]}}]}