Security readout for executives and security teams
Plain-English summary
Grafana installations before 8.5.14 or 9.1.8 can be tricked into accepting a malicious plugin even when unsigned plugins are blocked. The realistic path requires convincing a server administrator to install the plugin, so urgency depends on who can manage plugins and whether plugin sources are tightly controlled.
Executive priority
Treat as a moderate-priority remediation for Grafana environments with active plugin administration. Prioritize systems where many admins can install plugins or where plugin supply-chain controls are weak.
Technical view
This is a CWE-347 signature verification bypass in Grafana plugin handling. An attacker can get a malicious plugin run despite unsigned-plugin restrictions if a server admin downloads and installs it. CVSS 3.1 is 6.1, with high confidentiality and integrity impact and low availability impact.
Likely exposure
Exposure is most likely in self-managed Grafana versions below 8.5.14, or 9.0.0 through 9.1.7, where admins install plugins. The sources do not show unauthenticated remote exploitation.
Exploitation context
The source bundle does not identify active exploitation or CISA KEV listing. Exploitation depends on admin interaction: a server administrator must be convinced to download and run a malicious plugin from an untrusted source.
Researcher notes
Evidence supports a plugin signature bypass with required admin interaction, not broad remote compromise. NetApp published a related advisory, but the provided bundle does not include detailed affected NetApp product mapping.
Mitigation direction
- Upgrade Grafana to 8.5.14, 9.1.8, or later supported versions.
- Do not install plugins from untrusted sources.
- Review plugin installation permissions and administrator access.
- Check Grafana and downstream vendor advisories for environment-specific guidance.
Validation and detection
- Inventory Grafana versions across production and managed environments.
- Confirm instances are not below 8.5.14 or between 9.0.0 and 9.1.7.
- Review installed plugins and their source provenance.
- Check administrative audit logs for recent plugin installs.
- Verify unsigned-plugin restrictions and plugin governance controls.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-31123 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:L0.65.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.1MediumVector: CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:L
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.