CVE-2023-45807

Mitigation

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.

For more information

If you have any questions or comments about this advisory, please contact AWS/Amazon Security via our issue reporting page (https://aws.amazon.com/security/vulnerability-reporting/) or directly via email to [email protected]. Please do not create a public GitHub issue.

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.

CVE-2023-45807 has a CVSS score of 5.4 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.11.0.0, 1.3.14.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2023-45807? CVE-2023-45807 is a medium-severity security vulnerability in org.opensearch.plugin:opensearch-security (maven), affecting versions >= 2.0.0.0, < 2.11.0.0. It is fixed in 2.11.0.0, 1.3.14.0.
2. How severe is CVE-2023-45807? CVE-2023-45807 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.opensearch.plugin:opensearch-security are affected by CVE-2023-45807? org.opensearch.plugin:opensearch-security (maven) versions >= 2.0.0.0, < 2.11.0.0 is affected.
4. Is there a fix for CVE-2023-45807? Yes. CVE-2023-45807 is fixed in 2.11.0.0, 1.3.14.0. Upgrade to this version or later.
5. Is CVE-2023-45807 exploitable, and should I be worried? Whether CVE-2023-45807 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-45807 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-45807?
   • Upgrade org.opensearch.plugin:opensearch-security to 2.11.0.0 or later
   • Upgrade org.opensearch.plugin:opensearch-security to 1.3.14.0 or later

Other vulnerabilities in org.opensearch.plugin:opensearch-security