dbcve.org
Enterprise MetricsApplication · Grafana

CVE-2021-31231

MEDIUM · 5.5 CVSS v3.1 Published 2021-04-30
Fix available
A fix is available. Upgrade to 1.2.1 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Alertmanager in Grafana Enterprise Metrics before 1.2.1 and Metrics Enterprise 1.2.1 has a local file disclosure vulnerability when experimental.alertmanager.enable-api is used. The HTTP basic auth password_file can be used as an attack vector to send any file content via a webhook. The alertmanager templates can be used as an attack vector to send any file content because the alertmanager can load any text file specified in the templates list.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a local file disclosure vulnerability in Grafana Enterprise Metrics and Metrics Enterprise (before 1.2.1). When the experimental.alertmanager.enable-api feature is enabled, an authenticated attacker can read arbitrary local files by leveraging either the HTTP basic auth password_file configuration or alertmanager template file loading capability, then exfiltrate the file contents via webhooks.

MitigationUpgrade to version 1.2.1 or later, or disable the experimental.alertmanager.enable-api feature if not required in production environments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise MetricsApplication
Affected:< 1.2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Grafana Enterprise Metrics is installed
    Locate the Grafana Enterprise Metrics binary or installation directory. Check the installed version using 'gem -v' or 'grafana-enterprise-metrics --version' if available, or examine version metadata in the installation package.
    Affected if The installed version is below 1.2.1
  2. Verify the experimental.alertmanager.enable-api feature flag
    Inspect the Grafana Enterprise Metrics configuration file (typically grafana-enterprise-metrics.yml or similar) for the setting 'experimental.alertmanager.enable-api' and confirm whether it is set to true or enabled.
    Affected if The feature flag experimental.alertmanager.enable-api is set to true or enabled in the configuration
  3. Check for HTTP basic auth with password_file configured
    Search the configuration files for any [auth.basic] section or 'password_file' directive that references a local file path for storing passwords.
    Affected if HTTP basic authentication is enabled with a password_file configuration pointing to a local file path
  4. Identify alertmanager webhook configurations
    Look for alertmanager configuration files or sections that define webhook receivers, particularly any that reference template files via 'template' directives.
    Affected if Alertmanager webhook receivers with template file references are configured

A user is affected if they run Grafana Enterprise Metrics version below 1.2.1 AND have experimental.alertmanager.enable-api enabled, with either HTTP basic auth using password_file or alertmanager webhook templates configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 1.2.1 or later
Fixed in 1.2.1
Interim mitigation

Upgrade to version 1.2.1 or later, or disable the experimental.alertmanager.enable-api feature if not required in production environments.

Fix this in Enterprise Metrics Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-31231 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-31231 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data