Critical Remote Code Execution Vulnerability in Metabase Puts Thousands of Instances at Risk

Metabase, a popular open-source business intelligence tool used for creating charts and dashboards with various databases and sources, has been found to have a critical remote code execution (RCE) vulnerability. This vulnerability potentially allows hackers to infiltrate servers and execute unauthorized commands. In light of this discovery, the developers of Metabase have released patches to address and mitigate the vulnerability. However, the exposure of over 20,000 instances of Metabase to the internet, coupled with the potential exposure of sensitive data sources, adds urgency to the need for users to upgrade to the latest version of Metabase.

Critical Remote Code Execution Vulnerability Uncovered

During a recent security audit, a critical remote code execution vulnerability was discovered in Metabase. This vulnerability allows malicious actors to gain unauthorized access to servers and execute arbitrary commands. The impact of such an exploit could be significant, as it compromises the integrity and security of the affected systems.

Patches have been released to address the vulnerability

In response to the discovery, the developers of Metabase acted swiftly to release patches that address the remote code execution vulnerability. These patches are designed to mitigate the risk posed by the vulnerability and safeguard Metabase users. It is crucial for all Metabase users to promptly update their systems with these patches to ensure the security of their installations.

Metabase: An Overview

Metabase is an open-source business intelligence tool that has gained popularity due to its versatility and ease of use. It allows users to create visually appealing charts, dashboards, and reports by connecting to various databases and data sources. Metabase has been embraced by organizations across industries as the go-to solution for their business intelligence and data visualization needs.

Exposure of Instances and Sensitive Data

Alarming reports indicate that more than 20,000 instances of Metabase were exposed to the internet at the time of the vulnerability discovery. This exposure becomes especially concerning as it potentially exposes sensitive data sources that are connected to these Metabase instances. Hackers who exploit the vulnerability can not only gain unauthorized access to the servers but also potentially access and manipulate critically important data.

Achieving pre-auth remote code execution

Researchers investigating the vulnerability devised a method to achieve pre-auth remote code execution. By starting a vulnerable Metabase instance on port 3000, they were able to exploit the vulnerability and execute unauthorized commands. This alarming discovery highlights the critical nature of the vulnerability and the urgent need for users to take action.

The Role of Setup Tokens in Metabase

During the initial setup process of Metabase, a setup token is provided to users. This setup token allows users to complete the setup and configuration of their Metabase instances. However, it has been found that in some instances, the setup token was accessible to unauthenticated users, potentially compromising the security of the system.

Accessibility of Setup Token for Unauthenticated Users

The researchers found various methods by which unauthenticated users could gain access to the setup token. This oversight introduces a significant vulnerability as unauthorized users can exploit the token to gain control over the Metabase instance and potentially execute unauthorized commands. It is essential for Metabase users to review their system configurations and ensure that the setup token is not accessible to unauthenticated users.

Instances where setup token was not removed

It has come to light that numerous instances of Metabase failed to properly remove the setup token, even after the initial setup process was complete. This oversight perpetuates the vulnerability and exposes the system to potential unauthorized access. Metabase users must be proactive in ensuring that the setup token is removed or properly secured to prevent exploitation.

SQL Injection Discovery in the H2 DB Driver

In addition to the critical remote code execution vulnerability, an SQL injection was also discovered in the H2 database driver used by Metabase. This injection vulnerability arises from the INIT parameter and poses further risks to the security and integrity of the affected systems. Users must update to the latest version of Metabase to mitigate this vulnerability.

Upgrade to the Latest Version: A Recommendation

Given the seriousness of the remote code execution vulnerability, the exposure of instances, and the discovery of the SQL injection, it is imperative that all Metabase users upgrade to the latest version. The patches released by the developers address the vulnerabilities and provide necessary safeguards. Upgrading to the latest version ensures that users are protected from potential unauthorized access and data breaches.

The discovery of a critical remote code execution vulnerability in Metabase raises concerns for thousands of instances exposed to the internet. The urgency to address this vulnerability is amplified by the potential exposure of sensitive data sources. The developers have released patches to mitigate the risk, but it is incumbent upon the users to promptly update their Metabase installations. By doing so, organizations can fortify their business intelligence systems, protect their data, and safeguard against unauthorized access and manipulation.

Explore more