CVE intelligence and bounded remediation
CVE-2021-41090 — Grafana Agent is a telemetry collector for sending metrics, logs, and trace data to the opinionated Grafana observability stack
Grafana Agent is a telemetry collector for sending metrics, logs, and trace data to the opinionated Grafana observability stack. Prior to versions 0.20.1 and 0.21.2, inline secrets defined within a metrics instance config are exposed in plaintext over two endpoints: metrics instance configs defined in the base YAML file are exposed at `/-/config` and metrics instance configs defined for the scraping service are exposed at `/agent/api/v1/configs/:key`. Inline secrets will be exposed to anyone being able to reach these endpoints. If HTTPS with client authentication is not configured, these endpoints are accessible to unauthenticated users. Secrets found in these sections are used for delivering metrics to a Prometheus Remote Write system, authenticating against a system for discovering Prometheus targets, and authenticating against a system for collecting metrics. This does not apply for non-inlined secrets, such as `*_file` based secrets. This issue is patched in Grafana Agent versions 0.20.1 and 0.21.2. A few workarounds are available. Users who cannot upgrade should use non-inline secrets where possible. Users may also desire to restrict API access to Grafana Agent with some comb…
- Severity
- High
- CVSS
- 7.5 (3.1)
- Published
- 2021-12-08
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-200, CWE-312
Affected products
- grafana / agent
Matched remediation archetype
Information disclosure and sensitive data exposure
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Trace sensitive data through responses, errors, logs, metrics, traces, caches, exports, files, backups, and client bundles.
- Identify affected subjects, tenants, retention windows, access controls, and downstream copies without opening unnecessary sensitive records.
- Review metadata, timing, status, length, and existence signals as well as direct content disclosure.
Remediate safely
- Minimize collection and output, apply field-level authorization and redaction at a centralized boundary, and return generic external errors.
- Remove secrets and sensitive data from logs, artifacts, URLs, caches, and client-side bundles; rotate credentials that may have been exposed.
- Update the affected component and add synthetic-data tests for response, error, observability, and export paths.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.