dbcve.org
KibanaApplication · Elastic

CVE-2022-23713

MEDIUM · 6.1 CVSS v3.1 Published 2022-07-06
Fix available
A fix is available. Upgrade to 7.17.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A cross-site-scripting (XSS) vulnerability was discovered in the Vega Charts Kibana integration which could allow arbitrary JavaScript to be executed in a victim’s browser.

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 confidence

A stored cross-site-scripting (XSS) vulnerability exists in the Vega Charts integration for Kibana. The vulnerability allows an attacker to inject malicious JavaScript into a Vega chart visualization, which then executes in the browsers of users who view that visualization.

MitigationUpdate Kibana to a version containing the security patch for this vulnerability, or implement input sanitization for the Vega Charts integration to neutralize malicious script payloads.

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
KibanaApplication
Affected:>= 7.0.0, < 7.17.5>= 8.0.0, <= 8.2.3

CVSS 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Kibana installation and version
    Run the command 'kibana --version' or check the 'package.json' version file in the Kibana installation directory. Alternatively, query the Kibana API endpoint '/api/status' which returns the version information.
    Affected if The installed version falls within >= 7.0.0 and < 7.17.5, OR >= 8.0.0 and <= 8.2.3.
  2. Confirm Vega plugin is enabled
    Check the Kibana configuration file 'kibana.yml' for the setting 'vega.enabled: true' or verify that Vega visualizations can be created in the Kibana UI under 'Visualize' > 'Vega' or 'Vega Lite'.
    Affected if The Vega plugin is enabled and users can create or edit Vega visualizations.
  3. Identify existing Vega visualizations
    Query the Kibana saved objects API endpoint '/api/saved_objects/_find?type=visualization' to list all visualizations, then filter for those with 'vesicured' type or check the Kibana UI for any visualizations using the Vega or Vega Lite visualization types.
    Affected if Any Vega or Vega Lite visualizations exist in the Kibana environment.
  4. Assess user access to visualization creation
    Review Kibana roles and permissions to determine which users have privileges to create or edit visualizations. Check the 'kibana.yml' configuration for role-based access control settings and review assigned roles in the 'Security' or 'Management' section.
    Affected if Users other than trusted administrators can create or modify visualizations in Kibana.

A Kibana installation is affected if it runs a version within the ranges 7.0.0 to 7.17.4 or 8.0.0 to 8.2.3, has the Vega plugin enabled, contains Vega visualizations, and permits untrusted users to create or view those visualizations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 7.17.5 or later
Fixed in 7.17.5
Interim mitigation

Update Kibana to a version containing the security patch for this vulnerability, or implement input sanitization for the Vega Charts integration to neutralize malicious script payloads.

Recommended fix Moderate confidence

Kibana 7.17.5 or higher (7.x line); Kibana 8.2.4 or higher (8.x line)

  1. 1. Backup your current Kibana configuration and data
  2. 2. Ensure Elasticsearch version is compatible with the target Kibana version before upgrading
  3. 3. Download the fixed Kibana version (7.17.5+ for 7.x line, or 8.2.4+ for 8.x line) from elastic.co/downloads/kibana
  4. 4. Stop the Kibana service
  5. 5. Install the new Kibana version
  6. 6. Verify configuration files are compatible with the new version
  7. 7. Start the Kibana service
  8. 8. Test the Vega Charts functionality to confirm the fix
Caveat Review Elastic Stack compatibility matrix; some plugin compatibility may be affected; upgrade Elasticsearch first if needed to match version requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kibana Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23713 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-23713 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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