Metabase up to 1.46.6.3 /api/database code injection

Summaryinfo

A vulnerability has been found in Metabase up to 1.46.6.3 and classified as critical. This issue affects some unknown processing of the file /api/database. The manipulation leads to code injection. This vulnerability is documented as CVE-2023-37470. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Metabase up to 1.46.6.3. It has been rated as critical. This issue affects an unknown part of the file /api/database. The manipulation with an unknown input leads to a code injection vulnerability. Using CWE to declare the problem leads to CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was released 08/04/2023 as GHSA-p7w3-9m58-rq83. The advisory is shared at github.com. The identification of this vulnerability is CVE-2023-37470 since 07/06/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.

Upgrading to version 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 or 1.46.6.4 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Metabase

Version

• 0.43.7.0
• 0.43.7.1
• 0.43.7.2
• 0.44.7.0
• 0.44.7.1
• 0.44.7.2
• 0.45.4.0
• 0.45.4.1
• 0.45.4.2
• 0.46.6.0
• 0.46.6.1
• 0.46.6.2
• 0.46.6.3
• 1.43.7.0
• 1.43.7.1
• 1.43.7.2
• 1.44.7.0
• 1.44.7.1
• 1.44.7.2
• 1.45.4.0
• 1.45.4.1
• 1.45.4.2
• 1.46.6.0
• 1.46.6.1
• 1.46.6.2
• 1.46.6.3

Website

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

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion