GHSA-9j4f-f249-q5w8

Suggest an improvement
Source
https://github.com/advisories/GHSA-9j4f-f249-q5w8
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/09/GHSA-9j4f-f249-q5w8/GHSA-9j4f-f249-q5w8.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-9j4f-f249-q5w8
Aliases
Published
2024-09-06T21:37:02Z
Modified
2024-09-06T21:37:02Z
Severity
  • 7.2 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N CVSS Calculator
  • 6.9 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N CVSS Calculator
Summary
Default installation of `synthetic-monitoring-agent` exposes sensitive information
Details

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:

For more information

If you have any questions or comments about this advisory: * You can use the Synthetic Monitoring Agent discussions. * Issues should be reported in the Synthetic Monitoring Agent issues. * Email us at security@grafana.com.

References

Affected packages

Go / github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent

Package

Name
github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent
View open source insights on deps.dev
Purl
pkg:golang/github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.12.0

Go / github.com/grafana/synthetic-monitoring-agent

Package

Name
github.com/grafana/synthetic-monitoring-agent
View open source insights on deps.dev
Purl
pkg:golang/github.com/grafana/synthetic-monitoring-agent

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.12.0