dbcve.org
KibanaApplication · Elastic

CVE-2024-37287

HIGH · 7.2 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 7.17.23 / 8.14.2 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
A flaw allowing arbitrary code execution was discovered in Kibana. An attacker with access to ML and Alerting connector features, as well as write access to internal ML indices can trigger a prototype pollution vulnerability, ultimately leading to arbitrary code execution.

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 versions prior to the patch contain a prototype pollution vulnerability that can be triggered by an attacker with access to ML and Alerting connector features combined with write access to internal ML indices. This allows the attacker to pollute JavaScript object prototypes, ultimately achieving arbitrary code execution on the Kibana server.

MitigationUpgrade Kibana to the version containing the security patch. Restrict access to ML and Alerting connector features and limit write access to internal ML indices until the patch is applied.

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.7.0, < 7.17.23>= 8.0.0, < 8.14.2

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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. Identify Kibana version
    Run 'kibana --version' or check the version file in the Kibana installation directory, or query the Kibana API endpoint /api/status
    Affected if The installed version is 7.7.0 through 7.17.22 inclusive, or 8.0.0 through 8.14.1 inclusive
  2. Confirm ML plugin is enabled
    Check kibana.yml configuration file for 'ml.enabled: true' setting, or verify via /api/status ML plugin status endpoint
    Affected if ML plugin is enabled (this is often enabled by default in many deployments)
  3. Verify Alerting connector access
    Check user/role permissions in Kibana Security settings for access to Alerting connector features, or review role-based access control configuration
    Affected if Users or roles have write access to Alerting connectors
  4. Check for write access to internal ML indices
    Review Kibana role permissions or Elasticsearch index permissions for write access to .ml-* internal indices
    Affected if Any user has write permissions to internal ML indices (.ml-*) combined with ML and Alerting access

You are affected if your Kibana version falls within the vulnerable ranges AND both ML plugin and Alerting connector features are accessible to users who also have write access to internal ML indices.

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.23 / 8.14.2 or later
Fixed in 7.17.238.14.2
Interim mitigation

Upgrade Kibana to the version containing the security patch. Restrict access to ML and Alerting connector features and limit write access to internal ML indices until the patch is applied.

Recommended fix High confidence

Kibana 7.17.23 or 8.14.2 (depending on your major version branch)

  1. 1. Verify current Kibana version by checking the Kibana logs or status endpoint
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Take a backup of Kibana configuration and data directories
  4. 4. Upgrade Kibana to version 7.17.23 (for 7.x deployments) or 8.14.2 (for 8.x deployments)
  5. 5. Verify the upgrade was successful by checking Kibana status and logs
  6. 6. Confirm that ML and Alerting connector features are functioning correctly post-upgrade
Caveat Review Elastic Stack upgrade guides for potential breaking changes between your current version and the target version, particularly around ML job configurations and alerting connector permissions

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

Fix this in Kibana Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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