External risk intelligence

MeterSphere Pre-Authentication Code Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2022-51027

MeterSphere is an enterprise-grade continuous testing platform typically deployed as a centralized web application. The vulnerable endpoints are part of the core plugin management system. As a web-based testing platform, it is commonly exposed as an internal or external web service accessible to developers and QA teams, making it a likely target for network-based reachability in standard enterprise deployments.

Missing Authentication

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability has been identified in MeterSphere software that could allow unauthorized access to execute arbitrary code. This issue stems from improperly secured plugin management features, meaning an attacker could potentially upload and run malicious code without needing any credentials. The primary concern is to confirm if our environment utilizes this specific software and is therefore exposed.

  • Code injection flaw in plugin system.
  • Potential for unauthorized code execution.
  • Confirm MeterSphere usage and exposure.

Attack Path

How an attacker could exploit the issue

Attackers can exploit this vulnerability by reaching exposed plugin endpoints on MeterSphere without needing to log in. By uploading a malicious file and then invoking it through specific parameters, an attacker can achieve remote code execution on the server.

  • No authentication required to access.
  • Invokes vulnerable plugin endpoints.
  • Leads to remote code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to execute arbitrary code on the server when supported by the advisory's configuration. This could impact system integrity and confidentiality.

  • Server-side code execution is at risk.
  • Attackers upload and invoke malicious jars.
  • Compromise of the testing platform.

Operational Fix

Recommended remediation, mitigation, and detection steps

In real-world deployments, the responsibility for addressing this pre-authentication code injection vulnerability likely falls across application owners, infrastructure teams, and potentially vendor management if MeterSphere is a third-party tool. The first practical step is to identify all instances of MeterSphere, determine their reachability and business criticality, and then confirm the accountable owner for each deployment to plan remediation based on assessed risk.

  • App owners and infrastructure teams.
  • Verify MeterSphere reachability and criticality.
  • Plan vendor coordination and remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is MeterSphere?

MeterSphere is an enterprise-grade continuous testing platform designed to streamline software quality assurance. It provides tools for interface testing, performance testing, and UI automation. Because it functions as a centralized web application, teams often host it as a shared internal or external service to manage testing projects and coordinate development efforts.

What is the code injection vulnerability in CVE-2022-51027?

This is a pre-authentication code injection flaw, specifically categorized as CWE-306: Missing Authentication for Critical Function. The vulnerability occurs because certain plugin management endpoints do not verify user identity. This allows an unauthorized user to interact with the system as if they were an administrator, potentially running arbitrary code on the server.

How do attackers trigger this vulnerability?

An attacker triggers the bug by sending specifically crafted HTTP requests to the plugin endpoints. The process involves uploading a malicious JAR file and then invoking it using defined parameters. Crucially, this does not require a valid login session or any pre-existing credentials; simply reaching the affected network endpoints is sufficient.

Is my MeterSphere instance at risk?

According to Halo Surface Signal, MeterSphere is often deployed as a web-accessible service for testing teams, making it a likely target. If your installation is reachable over the network—whether internally or via the internet—it may be exposed to this flaw. You should evaluate your network perimeter to determine if these specific plugin endpoints are accessible.

What should I do if I use MeterSphere?

First, identify all active instances of MeterSphere within your environment and confirm their current versions. Once you have an inventory, coordinate with your infrastructure and application owners to assess the risk of each deployment. Review vendor-provided updates to apply the necessary patches and prioritize securing systems that are reachable over the network.

References