CVE-2023-5123: Improper Path Sanitization in JSON Datasource Plugin
The JSON datasource plugin ( https://grafana.com/grafana/plugins/marcusolsson-json-datasource/ ) is a Grafana Labs maintained plugin for Grafana that allows for retrieving and processing JSON data from a remote endpoint (including a specific sub-path) configured by an administrator. Due to inadequate sanitization of the dashboard-supplied path parameter, it was possible to include path traversal characters (../) in the path parameter and send requests to paths on the configured endpoint outside the configured sub-path.
This means that if the datasource was configured by an administrator to point at some sub-path of a domain (e.g. https://example.com/api/somesafeapi/ ), it was possible for an editor to create a dashboard referencing the datasource which issues queries containing path traversal characters, which would in turn cause the datasource to instead query arbitrary subpaths on the configured domain (e.g. https://example.com/api/adminapi/) .
In the rare case that this plugin is configured by an administrator to point back at the Grafana instance itself, this vulnerability becomes considerably more severe, as an administrator browsing a maliciously configured panel could be compelled to make requests to Grafana administrative API endpoints with their credentials, resulting in the potential for privilege escalation, hence the high score for this vulnerability.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2023-5123?
CVE-2023-5123 has been classified with a severity rating that indicates it poses a significant risk to systems using the JSON datasource plugin.
How do I fix CVE-2023-5123?
To fix CVE-2023-5123, update the JSON datasource plugin to the latest version provided by Grafana Labs.
Which software is affected by CVE-2023-5123?
CVE-2023-5123 affects the JSON datasource plugin maintained by Grafana Labs.
What types of vulnerabilities does CVE-2023-5123 represent?
CVE-2023-5123 represents vulnerabilities related to improper processing of JSON data from remote endpoints.
Can I mitigate CVE-2023-5123 without updating?
Mitigating CVE-2023-5123 without updating is not recommended, but reviewing and restricting access to the JSON datasource configuration can provide temporary protection.