CVE-2022-46156

The Synthetic Monitoring Agent for Grafana's Synthetic Monitoring application provides probe functionality and executes network checks for monitoring remote targets. Users running the Synthetic Monitoring agent prior to version 0.12.0 in their local network are impacted. The authentication token used to communicate with the Synthetic Monitoring API is exposed through a debugging endpoint. This token can be used to retrieve the Synthetic Monitoring checks created by the user and assigned to the agent identified with that token. The Synthetic Monitoring API will reject connections from already-connected agents, so access to the token does not guarantee access to the checks. Version 0.12.0 contains a fix. Users are advised to rotate the agent tokens. After upgrading to version v0.12.0 or later, it's recommended that users of distribution packages review the configuration stored in `/etc/synthetic-monitoring/synthetic-monitoring-agent.conf`, specifically the `API_TOKEN` variable which has been renamed to `SM_AGENT_API_TOKEN`. As a workaround for previous versions, it's recommended that users review the agent settings and set the HTTP listening address in a manner that limits the exposure, for example, localhost or a non-routed network, by using the command line parameter `-listen-address`, e.g. `-listen-address localhost:4050`.

The Synthetic Monitoring Agent for Grafana's Synthetic Monitoring application provides probe functionality and executes network checks for monitoring remote targets. Users running the Synthetic Monitoring agent prior to version 0.12.0 in their local network are impacted. The authentication token used to communicate with the Synthetic Monitoring API is exposed through a debugging endpoint. This token can be used to retrieve the Synthetic Monitoring checks created by the user and assigned to the agent identified with that token. The Synthetic Monitoring API will reject connections from already-connected agents, so access to the token does not guarantee access to the checks. Version 0.12.0 contains a fix. Users are advised to rotate the agent tokens. After upgrading to version v0.12.0 or later, it's recommended that users of distribution packages review the configuration stored in `/etc/synthetic-monitoring/synthetic-monitoring-agent.conf`, specifically the `API_TOKEN` variable which has been renamed to `SM_AGENT_API_TOKEN`. As a workaround for previous versions, it's recommended that users review the agent settings and set the HTTP listening address in a manner that limits the exposure, for example, localhost or a non-routed network, by using the command line parameter `-listen-address`, e.g. `-listen-address localhost:4050`.

Grafana's default installation of `synthetic-monitoring-agent` exposes sensitive information in github.com/grafana/synthetic-monitoring-agent

### Impact Users running the Synthetic Monitoring agent in their local network are impacted. The authentication token used to communicate with the Synthetic Monitoring API is exposed thru a debugging endpoint. This token can be used to retrieve the Synthetic Monitoring checks created by the user and assigned to the agent identified with that token. The Synthetic Monitoring API will reject connections from already-connected agents, so access to the token does not guarantee access to the checks. ### Patches Fixed version is v0.12.0 Users are advised to rotate the agent tokens. After upgrading to version v0.12.0 or later, it's recommended that user's of distribution packages (e.g. Debian or RedHat and their derivatives) review the configuration stored in `/etc/synthetic-monitoring/synthetic-monitoring-agent.conf`, specifically the `API_TOKEN` variable which has been renamed to `SM_AGENT_API_TOKEN`. ### Workarounds With all previous versions, it's recommended that users review the agent settings and set the HTTP listening address in a manner that limits the exposure, for example, localhost or a non-routed network, by using the command line parameter `-listen-address`, e.g. `-listen-address localhost:4050`. ### References The following changes have been made to address this issue: - [Disable debug endpoint by default](https://github.com/grafana/synthetic-monitoring-agent/pull/373) - [Allow retrieving the token from the environment](https://github.com/grafana/synthetic-monitoring-agent/pull/374) - [Default to listening on localhost](https://github.com/grafana/synthetic-monitoring-agent/pull/375) ### For more information If you have any questions or comments about this advisory: * You can use the [Synthetic Monitoring Agent discussions](https://github.com/grafana/synthetic-monitoring-agent/discussions). * Issues should be reported in the [Synthetic Monitoring Agent issues](https://github.com/grafana/synthetic-monitoring-agent/issues). * Email us at [security@grafana.com](mailto:security@grafana.com).

El agente de monitoreo sintético para la aplicación Synthetic Monitoring de Grafana proporciona funcionalidad de sonda y ejecuta comprobaciones de red para monitorizar objetivos remotos. Los usuarios que ejecutan el agente de Synthetic Monitoring antes de la versión 0.12.0 en su red local se ven afectados. El token de autenticación utilizado para comunicarse con la API de Synthetic Monitoring se expone a través de un endpoint de depuración. Este token se puede utilizar para recuperar las comprobaciones de Synthetic Monitoring creadas por el usuario y asignadas al agente identificado con ese token. La API de Synthetic Monitoring rechazará conexiones de agentes ya conectados, por lo que el acceso al token no garantiza el acceso a las comprobaciones. La versión 0.12.0 contiene la solución. Se recomienda a los usuarios rotar los tokens de los agentes. Después de actualizar a la versión v0.12.0 o posterior, se recomienda que los usuarios de los paquetes de distribución revisen la configuración almacenada en `/etc/synthetic-monitoring/synthetic-monitoring-agent.conf`, específicamente la variable `API_TOKEN` cuyo nombre ha sido renombrado a `SM_AGENT_API_TOKEN`. Como workaround para versiones anteriores, se recomienda que los usuarios revisen la configuración del agente y establezcan la dirección de escucha HTTP de una manera que limite la exposición, por ejemplo, localhost o una red no enrutada, utilizando el parámetro de línea de comando `-listen-address`, p.e. `-listen-address localhost:4050`.