# CVE-2023-45807: OpenSearch Issue with tenant read-only permissions > Authenticated users with read-only tenant access can modify or delete dashboard metadata, potentially causing denial of service for visualizations. - **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 16 Oct 2023 - **Updated:** 13 Sep 2024 - **Also known as:** GHSA-72q2-gwwf-6hrv, UBUNTU-CVE-2023-45807 ## What is CVE-2023-45807? CVE-2023-45807 is a medium-severity missing authorization vulnerability in opensearch-project security, published on 16 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-281 (Improper Preservation of Permissions) ## Which versions are affected by CVE-2023-45807? 4 open source packages ship an affected version, including org.opensearch.plugin:opensearch-security. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.opensearch.plugin:opensearch-security` | Maven | All versions | 1.3.14.0 | | `org.opensearch.plugin:opensearch-security` | Maven | All versions | 1.3.14.0 | | `org.opensearch.plugin:opensearch-security` | Maven | From 2.0.0.0 | 2.11.0.0 | | `org.opensearch.plugin:opensearch-security` | Maven | From 2.0.0.0 | 2.11.0.0 | Products: Amazon Opensearch. ## How do I fix CVE-2023-45807? Upgrade org.opensearch.plugin:opensearch-security to a fixed version for your release line: 1.3.14.0 or 2.11.0.0. ## Is CVE-2023-45807 being exploited? There is no known exploitation of CVE-2023-45807 in the wild and no public exploit code. ## Other vulnerabilities in opensearch-project security - [CVE-2022-31115](https://insights.sbomify.com/CVE-2022-31115/): Unsafe YAML deserialization in opensearch-ruby (high 8.8) - [CVE-2025-9624](https://insights.sbomify.com/CVE-2025-9624/): OpenSearch 3.2.0 - Nested Boolean/Disjunction asymmetric DoS (high 8.3) - [CVE-2022-35980](https://insights.sbomify.com/CVE-2022-35980/): OpenSearch vulnerable to Improper Authorization of Index Containing Sensitive Information (high 7.5) - [CVE-2022-41918](https://insights.sbomify.com/CVE-2022-41918/): Issue with fine-grained access control of indices backing data streams (medium 6.3) - [CVE-2023-23933](https://insights.sbomify.com/CVE-2023-23933/): Issue in Anomaly Detection with document and field level rules in numerical feature aggregations (medium 5.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-45807 and fix it if it is affected. What it is: CVE-2023-45807 is a medium-severity missing authorization vulnerability in opensearch-project security, published on 16 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-45807 in the wild and no public exploit code. Affected packages and fixed versions: - org.opensearch.plugin:opensearch-security (Maven): affected all versions; fixed in 1.3.14.0 - org.opensearch.plugin:opensearch-security (Maven): affected all versions; fixed in 1.3.14.0 - org.opensearch.plugin:opensearch-security (Maven): affected from 2.0.0.0; fixed in 2.11.0.0 - org.opensearch.plugin:opensearch-security (Maven): affected from 2.0.0.0; fixed in 2.11.0.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-45807/ (Markdown: https://insights.sbomify.com/CVE-2023-45807/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-45807 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-45807 - OSV: https://osv.dev/vulnerability/CVE-2023-45807 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-45807/ Summaries are generated and may contain mistakes; the official description above is the record.