CVE-2022-46156

{"id": "CVE-2022-46156", "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 3.3, "attackVector": "LOCAL", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "LOW"}, "impactScore": 1.4, "exploitabilityScore": 1.8}, {"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 7.2, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 2.7, "exploitabilityScore": 3.9}]}, "published": "2022-11-30T22:15:10.640", "references": [{"url": "https://github.com/grafana/synthetic-monitoring-agent/commit/d8dc7f9c1c641881cbcf0a09e178b90ebf0f0228", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/grafana/synthetic-monitoring-agent/pull/373", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/grafana/synthetic-monitoring-agent/pull/374", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/grafana/synthetic-monitoring-agent/pull/375", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/grafana/synthetic-monitoring-agent/releases/tag/v0.12.0", "tags": ["Release Notes", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/grafana/synthetic-monitoring-agent/security/advisories/GHSA-9j4f-f249-q5w8", "tags": ["Mitigation", "Third Party Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "NVD-CWE-Other"}]}, {"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-489"}, {"lang": "en", "value": "CWE-749"}]}], "descriptions": [{"lang": "en", "value": "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`."}, {"lang": "es", "value": "El agente de monitoreo sint\u00e9tico para la aplicaci\u00f3n 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\u00f3n 0.12.0 en su red local se ven afectados. El token de autenticaci\u00f3n utilizado para comunicarse con la API de Synthetic Monitoring se expone a trav\u00e9s de un endpoint de depuraci\u00f3n. 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\u00e1 conexiones de agentes ya conectados, por lo que el acceso al token no garantiza el acceso a las comprobaciones. La versi\u00f3n 0.12.0 contiene la soluci\u00f3n. Se recomienda a los usuarios rotar los tokens de los agentes. Despu\u00e9s de actualizar a la versi\u00f3n v0.12.0 o posterior, se recomienda que los usuarios de los paquetes de distribuci\u00f3n revisen la configuraci\u00f3n almacenada en `/etc/synthetic-monitoring/synthetic-monitoring-agent.conf`, espec\u00edficamente 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\u00f3n del agente y establezcan la direcci\u00f3n de escucha HTTP de una manera que limite la exposici\u00f3n, por ejemplo, localhost o una red no enrutada, utilizando el par\u00e1metro de l\u00ednea de comando `-listen-address`, p.e. `-listen-address localhost:4050`."}], "lastModified": "2022-12-05T14:58:13.157", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:grafana:synthetic_monitoring_agent:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "B0243C5D-EDC8-4238-94FF-0A7F6FDAF3C5", "versionEndExcluding": "0.12.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}