dbcve.org
KibanaApplication · Elastic

CVE-2023-31422

HIGH · 7.5 CVSS v3.1 Published 2023-10-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
An issue was discovered by Elastic whereby sensitive information is recorded in Kibana logs in the event of an error. The issue impacts only Kibana version 8.10.0 when logging in the JSON layout or when the pattern layout is configured to log the %meta pattern. Elastic has released Kibana 8.10.1 which resolves this issue. The error object recorded in the log contains request information, which can include sensitive data, such as authentication credentials, cookies, authorization headers, query params, request paths, and other metadata. Some examples of sensitive data which can be included in the logs are account credentials for kibana_system, kibana-metricbeat, or Kibana end-users.

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 · high confidence

Kibana 8.10.0 logs sensitive request data (authentication credentials, cookies, authorization headers, query parameters, and request paths) in plaintext to error logs when using JSON layout or pattern layout with %meta pattern. This exposes credentials for system accounts (kibana_system, kibana-metricbeat) and end-user credentials.

MitigationUpgrade Kibana to version 8.10.1 or later to resolve the issue. Alternatively, avoid using JSON layout or %meta pattern until patched.

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:= 8.10.0

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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

  1. Verify Kibana version is 8.10.0
    Run `bin/kibana --version` or check the version in the Kibana header in the UI, or query the status API at `GET /api/status`
    Affected if Version is exactly 8.10.0 (not 8.10.1 or later)
  2. Identify logging layout configuration
    Inspect the Kibana configuration file (kibana.yml) for `logging.dest` and any custom logging appender configurations. Check if the logging layout is set to JSON format.
    Affected if Logging output uses JSON layout or any JSON-formatted output configuration
  3. Check for %meta pattern in log patterns
    Review the Kibana logging configuration for any pattern-based layouts that include `%meta` in the pattern string.
    Affected if Log patterns contain %meta pattern for request metadata
  4. Inspect error logs for sensitive data
    Examine Kibana error logs (at the configured log destination) for plaintext instances of authorization headers, cookies, query parameters, or credentials.
    Affected if Logs contain plaintext credentials, cookies, or authorization headers from HTTP requests

Your environment is affected only if Kibana version is exactly 8.10.0 AND logging is configured to use JSON layout or %meta pattern in pattern layout.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Kibana to version 8.10.1 or later to resolve the issue. Alternatively, avoid using JSON layout or %meta pattern until patched.

Recommended fix High confidence

Kibana 8.10.1

  1. Download Kibana version 8.10.1 from the official Elastic download page
  2. Stop the Kibana service
  3. Backup your current Kibana configuration and data directories
  4. Install Kibana 8.10.1
  5. Verify the installation by checking the version number
  6. Start the Kibana service
  7. Monitor logs to confirm no sensitive data is being written to logs in error scenarios

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

Fix this in Kibana Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31422 — 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-2023-31422 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