Metabase vulnerable to remote code execution via POST /api/setup/validate API endpoint

Summary

Metabase is an open-source business intelligence and analytics platform. Prior to versions 0.43.7.3, 0.44.7.3, 0.45.4.3, 0.46.6.4, 1.43.7.3, 1.44.7.3, 1.45.4.3, and 1.46.6.4, a vulnerability could potentially allow remote code execution on one's Metabase server. The core issue is that one of the supported data warehouses (an embedded in-memory database H2), exposes a number of ways for a connection string to include code that is then executed by the process running the embedded database. Because Metabase allows users to connect to databases, this means that a user supplied string can be used to inject executable code. Metabase allows users to validate their connection string before adding a database (including on setup), and this validation API was the primary vector used as it can be called without validation. Versions 0.43.7.3, 0.44.7.3, 0.45.4.3, 0.46.6.4, 1.43.7.3, 1.44.7.3, 1.45.4.3, and 1.46.6.4 fix this issue by removing the ability of users to add H2 databases entirely. As a workaround, it is possible to block these vulnerabilities at the network level by blocking the endpoints `POST /api/database`, `PUT /api/database/:id`, and `POST /api/setup/validateuntil`. Those who use H2 as a file-based database should migrate to SQLite.

Timeline

1. Aug 4, 2023, 3:12 PM UTCCVE published
2. Oct 17, 2024, 2:54 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: total

3. Oct 17, 2024, 2:54 PM UTCRecord last updated

Affected versions

• metabase metabase

  fixed in 0.43.7.3; From 0.44.0.0 · fixed in 0.44.7.3; From 0.45.0.0 · fixed in 0.45.4.3; From 0.46.0.0 · fixed in 0.46.6.4; From 1.0.0 · fixed in 1.43.7.3; From 1.44.0.0 · fixed in 1.44.7.3; From 1.45.0.0 · fixed in 1.45.4.3; From 1.46.0.0 · fixed in 1.46.6.4

References 1