Sign inStart freeBook a demo

What is CVE-2022-46156?A low-severity flaw in Synthetic Monitoring Agent, explained.

Low severity1 affected product
The short answer

CVE-2022-46156 is a low-severity flaw (CVSS 3.3) in Synthetic Monitoring Agent from Grafana, published on 30 November 2022. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.5%. If you run an affected version, plan in the vendor’s fix.

Check if it affects you →How to fix it

Published 30 November 2022. Record last updated 5 December 2022. We keep this page's data up to date.

What it does

What is CVE-2022-46156? In plain terms.

An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read some data.

The official description

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`.

What kind of flaw is it?

  • CWE-489Active Debug Code
  • CWE-749Exposed Dangerous Method or Function
CVSS 3.1 scoreLow · 3.3

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAlready on the device
  • How hard it is to pull offEasy: no special conditions
  • Login needed firstAn ordinary user account
  • Does someone have to clickNo, nobody has to do anything
  • What an attacker getsCan read some data

Severity vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation

Is CVE-2022-46156 being exploited? Not that we know of.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.5%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days0.5%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Record last updated
How Precursor Intelligence ranks it
46out of 100Medium

CVE-2022-46156 scores 46. Action: Plan remediation.

We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:

  • Evidence it is being exploitedBiggest factor
  • How severe it isStrong factor
  • How widely exposed it isSmaller factor
  • Threat activity around itSmaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2022-46156 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2022-46156? One product.

The published record lists 1 product from 1 vendor. Versions are shown as published: "before 0.12.0" means every version up to, but not including, 0.12.0. If you run one of these, check your version, then go to the fix below.

Remediation

How do I fix CVE-2022-46156? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
  3. If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
  4. Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

References

6 links
Precursor Intelligence

Does CVE-2022-46156 affect you? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2022-46156 is a low-severity flaw in Synthetic Monitoring Agent from Grafana, published on 30 November 2022. An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read some data.

It scores 3.3 out of 10 on the CVSS severity scale, which is low. Our risk score for CVE-2022-46156 is 46 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.5%. That can change at any time, which is why we keep watching.

For Synthetic Monitoring Agent from Grafana: before 0.12.0.

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

Keep exploring