dbcve.org
OpensearchApplication · Amazon

CVE-2023-45807

MEDIUM · 5.4 CVSS v3.1 Published 2023-10-16
Fix available
A fix is available. Upgrade to 1.3.14.0 / 2.11.0.0 or later.
See remediation →
60/100
Remediation priority · Elevated
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
OpenSearch is a community-driven, open source fork of Elasticsearch and Kibana following the license change in early 2021. There is an issue with the implementation of tenant permissions in OpenSearch Dashboards where authenticated users with read-only access to a tenant can perform create, edit and delete operations on index metadata of dashboards and visualizations in that tenant, potentially rendering them unavailable. This issue does not affect index data, only metadata. Dashboards correctly enforces read-only permissions when indexing and updating documents. This issue does not provide additional read access to data users don’t already have. This issue can be mitigated by disabling the tenants functionality for the cluster. Versions 1.3.14 and 2.11.0 contain a fix for this issue.

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

OpenSearch Dashboards contains a broken access control vulnerability in its multi-tenant permission system where authenticated users granted read-only tenant access can nonetheless perform create, edit, and delete operations on dashboard and visualization index metadata, potentially causing denial of service for those resources. The issue stems from missing authorization checks on metadata operations while document-level read-only enforcement works correctly.

MitigationUpgrade OpenSearch Dashboards to version 1.3.14 or 2.11.0, or disable multi-tenant functionality if upgrading is not immediately feasible.

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
OpensearchApplication
Affected:< 1.3.14.0>= 2.0.0, < 2.11.0.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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 OpenSearch Dashboards version
    Check the installed OpenSearch Dashboards version. This is typically visible in the UI footer or can be queried via the _nodes/version API endpoint against the Dashboards service.
    Affected if The installed version falls outside the fixed releases: it is either below 1.3.14.0, or between 2.0.0.0 and 2.11.0.0 (exclusive).
  2. Confirm multi-tenant feature is enabled
    Inspect the OpenSearch Dashboards configuration file (opensearch_dashboards.yml) for the 'opensearch.multiTenant.enabled' setting, or query the tenant configuration via the OpenSearch Dashboards API.
    Affected if Multi-tenancy is enabled (setting value is true); the vulnerability only applies when this feature is active.
  3. Review user tenant role assignments
    Query the security plugin API to list users and their assigned tenant permissions. Specifically look for users assigned to any tenant with a read-only role such as 'kibana_read_only' or a custom read-only tenant role.
    Affected if There exist authenticated users who have been granted read-only tenant access, as these users could potentially exploit the broken authorization to modify metadata.

You are affected if your OpenSearch Dashboards version is vulnerable (before 1.3.14 or between 2.0.0 and 2.11.0), multi-tenancy is enabled, and users with read-only tenant permissions exist in the system.

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 1.3.14.0 / 2.11.0.0 or later
Fixed in 1.3.14.02.11.0.0
Interim mitigation

Upgrade OpenSearch Dashboards to version 1.3.14 or 2.11.0, or disable multi-tenant functionality if upgrading is not immediately feasible.

Recommended fix High confidence

1.3.14.0 (for 1.x branches) or 2.11.0.0 (for 2.x branches)

  1. Identify your current OpenSearch and OpenSearch Dashboards version using the/_cluster/health endpoint or Dashboardsabout page
  2. Determine which major version branch you are on (1.x or 2.x) to select the appropriate fixed release
  3. For OpenSearch 1.x: Upgrade both OpenSearch and OpenSearch Dashboards to version 1.3.14.0
  4. For OpenSearch 2.x: Upgrade both OpenSearch and OpenSearch Dashboards to version 2.11.0.0
  5. Verify the upgrade by checking the version numbers post-upgrade
  6. Confirm tenant permission restrictions are working as expected by testing with a read-only tenant user

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

Fix this in Opensearch Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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