CVE-2023-5122
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGrafana is an open-source platform for monitoring and observability. The CSV datasource plugin is a Grafana Labs maintained plugin for Grafana that allows for retrieving and processing CSV data from a remote endpoint configured by an administrator. If this plugin was configured to send requests to a bare host with no path (e.g. https://www.example.com/ https://www.example.com/` ), requests to an endpoint other than the one configured by the administrator could be triggered by a specially crafted request from any user, resulting in an SSRF vector. AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Grafana CSV datasource plugin, when configured with a bare host URL lacking an explicit path (e.g., https://www.example.com/), allows any authenticated user to craft special requests that trigger the plugin to make HTTP requests to arbitrary endpoints different from the administrator-configured target, resulting in Server-Side Request Forgery (SSRF).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.6.13CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify CSV datasource plugin is installedIn Grafana, navigate to Configuration > Plugins and search for 'CSV' or 'grafana-csv-datasource', or use the Grafana CLI: grafana cli plugins lsAffected if The plugin appears in the list of installed plugins
-
Check plugin versionIn Grafana UI, click on the CSV datasource plugin in the Plugins list to view its version, or check via CLI: grafana cli plugins list | grep -i csvAffected if Version is less than 0.6.13
-
Identify CSV datasource configurationsNavigate to Configuration > Data Sources in Grafana and identify any data sources using the CSV datasourceAffected if Any CSV datasource configurations exist
-
Inspect URL configuration for bare hostOpen each CSV datasource settings and examine the URL field. Determine if the URL contains only a hostname (e.g., https://www.example.com) without an explicit path componentAffected if The URL lacks a path (no / characters after the hostname)
You are affected if the CSV datasource plugin version is below 0.6.13 and any CSV datasource is configured with a bare host URL without an explicit path, which would allow authenticated users to trigger SSRF attacks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data0.6.13
Update the CSV datasource plugin to the latest patched version and ensure all CSV datasource configurations include explicit, complete paths rather than bare hostnames to prevent URL manipulation.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5122 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-5122 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data