Approved changes feed: RSS · Atom
cpe:2.3:a:opensearch-project:security:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Opensearch Project (4f1a5c8a-fdeb-57b7-acec-88c38c51999d) |
|---|---|
| Product | Security (5f15ebd1-22a6-5caf-af5a-7996fecbc383) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-45807 |
vulnerable | 2026-06-08 06:12:43.369444 |
OpenSearch Issue with tenant read-only permissions
MEDIUM (5.4)
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.
Published: 2023-10-16T21:33:23.124Z
Updated: 2024-09-13T18:59:11.668Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-31141 |
vulnerable | 2026-06-08 06:04:41.919460 |
OpenSearch issue with fine-grained access control during extremely rare race conditions
MEDIUM (4.8)
OpenSearch is open-source software suite for search, analytics, and observability applications. Prior to versions 1.3.10 and 2.7.0, there is an issue with the implementation of fine-grained access control rules (document-level security, field-level security and field masking) where they are not correctly applied to the queries during extremely rare race conditions potentially leading to incorrect access authorization. For this issue to be triggered, two concurrent requests need to land on the same instance exactly when query cache eviction happens, once every four hours. OpenSearch 1.3.10 and 2.7.0 contain a fix for this issue.
Published: 2023-05-08T20:33:58.601Z
Updated: 2025-01-29T14:54:25.850Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-25806 |
vulnerable | 2026-06-08 05:56:10.650071 |
Time discrepancy in authentication responses in OpenSearch
MEDIUM (5.3)
OpenSearch Security is a plugin for OpenSearch that offers encryption, authentication and authorization. There is an observable discrepancy in the authentication response time between calls where the user provided exists and calls where it does not. This issue only affects calls using the internal basic identity provider (IdP), and not other externally configured IdPs. Patches were released in versions 1.3.9 and 2.6.0, there are no workarounds.
Published: 2023-03-02T03:04:26.889Z
Updated: 2025-03-05T21:28:42.975Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-23613 |
vulnerable | 2026-06-08 05:56:03.776620 |
Field-level security issue with .keyword fields in OpenSearch
MEDIUM (5.7)
OpenSearch is an open source distributed and RESTful search engine. In affected versions there is an issue in the implementation of field-level security (FLS) and field masking where rules written to explicitly exclude fields are not correctly applied for certain queries that rely on their auto-generated .keyword fields. This issue is only present for authenticated users with read access to the indexes containing the restricted fields. This may expose data which may otherwise not be accessible to the user. OpenSearch 1.0.0-1.3.7 and 2.0.0-2.4.1 are affected. Users are advised to upgrade to OpenSearch 1.3.8 or 2.5.0. Users unable to upgrade may write explicit exclusion rules as a workaround. Policies authored in this way are not subject to this issue.
Published: 2023-01-24T20:33:55.673Z
Updated: 2025-03-10T21:20:32.391Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-23612 |
vulnerable | 2026-06-08 05:56:03.775320 |
Issue with whitespace in JWT roles in OpenSearch
MEDIUM (4.7)
OpenSearch is an open source distributed and RESTful search engine. OpenSearch uses JWTs to store role claims obtained from the Identity Provider (IdP) when the authentication backend is SAML or OpenID Connect. There is an issue in how those claims are processed from the JWTs where the leading and trailing whitespace is trimmed, allowing users to potentially claim roles they are not assigned to if any role matches the whitespace-stripped version of the roles they are a member of. This issue is only present for authenticated users, and it requires either the existence of roles that match, not considering leading/trailing whitespace, or the ability for users to create said matching roles. In addition, the Identity Provider must allow leading and trailing spaces in role names. OpenSearch 1.0.0-1.3.7 and 2.0.0-2.4.1 are affected. Users are advised to upgrade to OpenSearch 1.3.8 or 2.5.0. There are no known workarounds for this issue.
Published: 2023-01-24T20:36:41.876Z
Updated: 2025-03-10T21:20:26.061Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-41918 |
vulnerable | 2026-06-08 05:49:28.865085 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-35980 |
vulnerable | 2026-06-08 05:46:06.090911 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.