Metabase up to 1.46.2 missing authentication

Summaryinfo

A vulnerability, which was classified as critical, has been found in Metabase up to 1.46.2. This affects an unknown function. The manipulation leads to missing authentication. This vulnerability is documented as CVE-2023-32680. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Metabase up to 1.46.2. It has been rated as critical. This issue affects an unknown functionality. The manipulation with an unknown input leads to a missing authentication vulnerability. Using CWE to declare the problem leads to CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Metabase is an open source business analytics engine. To edit SQL Snippets, Metabase should have required people to be in at least one group with native query editing permissions to a database–but affected versions of Metabase didn't enforce that requirement. This lack of enforcement meant that: Anyone–including people in sandboxed groups–could edit SQL snippets. They could edit snippets via the API or, in the application UI, when editing the metadata for a model based on a SQL question, and people in sandboxed groups could edit a SQL snippet used in a query that creates their sandbox. If the snippet contained logic that restricted which data that person could see, they could potentially edit that snippet and change their level of data access. The permissions model for SQL snippets has been fixed in Metabase versions 0.46.3, 0.45.4, 0.44.7, 1.46.3, 1.45.4, and 1.44.7. Users are advised to upgrade. Users unable to upgrade should ensure that SQL queries used to create sandboxes exclude SQL snippets.

The weakness was released 05/19/2023 as GHSA-mw6j-f894-4qxv. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2023-32680 since 05/11/2023. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 0.44.7, 0.45.4, 0.46.3, 1.44.7, 1.45.4 or 1.46.3 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

• Metabase

Version

• 0.44.0
• 0.44.1
• 0.44.2
• 0.44.3
• 0.44.4
• 0.44.5
• 0.44.6
• 0.45.0
• 0.45.1
• 0.45.2
• 0.45.3
• 0.46.0
• 0.46.1
• 0.46.2
• 1.44.0
• 1.44.1
• 1.44.2
• 1.44.3
• 1.44.4
• 1.44.5
• 1.44.6
• 1.45.0
• 1.45.1
• 1.45.2
• 1.45.3
• 1.46.0
• 1.46.1
• 1.46.2

Website

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

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion