How severe is CVE-2022-46156?

CVE-2022-46156 has a CVSS score of 7.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2022-46156?

github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent (go) versions < 0.12.0; github.com/grafana/synthetic-monitoring-agent (go) versions < 0.12.0.

Is there a fix for CVE-2022-46156?

Yes. CVE-2022-46156 is fixed in 0.12.0. Upgrade to this version or later.

Is CVE-2022-46156 exploitable, and should I be worried?

Whether CVE-2022-46156 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-46156 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2022-46156

Q: What is CVE-2022-46156?

CVE-2022-46156 is a medium-severity security vulnerability in github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent (go), affecting versions < 0.12.0. It is fixed in 0.12.0.

Q: Is there a fix for CVE-2022-46156?

Yes. CVE-2022-46156 is fixed in 0.12.0. Upgrade to this version or later.

Q: Is CVE-2022-46156 exploitable, and should I be worried?

Whether CVE-2022-46156 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-46156 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-46156?

Upgrade: github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent to 0.12.0 or later, github.com/grafana/synthetic-monitoring-agent to 0.12.0 or later.

Summary

Default installation of synthetic-monitoring-agent exposes sensitive information

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 [email protected].

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.

CVE-2022-46156 has a CVSS score of 7.2 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.12.0); upgrading removes the vulnerable code path.

Affected versions

github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent (< 0.12.0) github.com/grafana/synthetic-monitoring-agent (< 0.12.0)

Security releases

github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent → 0.12.0 (go) github.com/grafana/synthetic-monitoring-agent → 0.12.0 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent to 0.12.0 or later; github.com/grafana/synthetic-monitoring-agent to 0.12.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-46156? CVE-2022-46156 is a medium-severity security vulnerability in github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent (go), affecting versions < 0.12.0. It is fixed in 0.12.0.
How severe is CVE-2022-46156? CVE-2022-46156 has a CVSS score of 7.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2022-46156?
- github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent (go) (versions < 0.12.0)
- github.com/grafana/synthetic-monitoring-agent (go) (versions < 0.12.0)
Is there a fix for CVE-2022-46156? Yes. CVE-2022-46156 is fixed in 0.12.0. Upgrade to this version or later.
Is CVE-2022-46156 exploitable, and should I be worried? Whether CVE-2022-46156 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-46156 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-46156?
- Upgrade github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent to 0.12.0 or later
- Upgrade github.com/grafana/synthetic-monitoring-agent to 0.12.0 or later