Skip to content

← Public intelligence

Go package

github.com/grafana/agent

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 4.0GoPublished

    Grafana Agent (Flow mode) on Windows has Unquoted Search Path or Element vulnerability

    CVE-2024-8996 · GHSA-m5gv-m5f9-wgv4

    Affected
    • Go github.com/grafana/agent < 0.43.3
    Fixed in
    0.43.3· Vendor fix available
    Issue
    Unquoted Search Path or Element vulnerability in Grafana Agent (Flow mode) on Windows allows Privilege Escalation from Local User to SYSTEM. This issue affects Agent Flow before 0.43.3.

    Recommended action: Upgrade to 0.43.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 6.5GoPublished

    Instance config inline secret exposure in Grafana

    CVE-2021-41090 · GHSA-9c4x-5hgq-q3wh

    Affected
    • Go github.com/grafana/agent >= 0.14.0, < 0.21.2
    Fixed in
    0.21.2· Vendor fix available
    Issue
    Impact Some inline secrets are exposed in plaintext over the Grafana Agent HTTP server: Inline secrets for metrics instance configs in the base YAML file are exposed at /-/config Inline secrets for integrations are exposed at /-/config Inline secrets for Consul ACL tokens and ETCD basic auth when configured for the scraping service at /-/config. Inline secrets for the Kafka receiver for OpenTelemetry-Collector tracing at /-/config. Inline secrets for metrics instance configs loaded from the scraping service are exposed at /agent/api/v1/configs/{name}. Inline secrets will be exposed to anyone being able to reach these endpoints. Secrets found in these sections are used for: Delivering metrics to a Prometheus Remote Write system Authenticating against a system for discovering Prometheus targets Authenticating against a system for collecting metrics (scrapeconfigs and integrations) Authenticating against a Consul or ETCD for storing configurations to distribute in scraping service mode…

    Recommended action: Upgrade to 0.21.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →