Vulnerabilities · 2023 · Metabase
CVE-2023-32680
Metabase vulnerability
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.
Affected products
Metabase. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Metabase runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/metabase/metabase/security/advisories/GHSA-mw6j-f894-4qxv · Vendor Advisory
- github.com/metabase/metabase/pull/30852 · Patch
- github.com/metabase/metabase/pull/30853 · Patch
- github.com/metabase/metabase/pull/30854 · Patch
- nvd.nist.gov/vuln/detail/CVE-2023-32680
- cve.org/CVERecord?id=CVE-2023-32680
More vulnerabilities in Metabase products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.