CVE-2023-45807 OpenSearch Issue with tenant read-only permissions

Medium 5.4 Published Updated

Authenticated users with read-only tenant access can modify or delete dashboard metadata, potentially causing denial of service for visualizations.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

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

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.

PackageAffectedFixed in
org.opensearch.plugin:opensearch-security MavenAll versions1.3.14.0
org.opensearch.plugin:opensearch-security MavenAll versions1.3.14.0
org.opensearch.plugin:opensearch-security MavenFrom 2.0.0.02.11.0.0
org.opensearch.plugin:opensearch-security MavenFrom 2.0.0.02.11.0.0

Products include 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.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2023-45807 being exploited?

There is no known exploitation of CVE-2023-45807 in the wild and no public exploit code.

Sources

Also known as GHSA-72q2-gwwf-6hrv, UBUNTU-CVE-2023-45807.

Is CVE-2023-45807 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free