Approved changes feed: RSS · Atom

cpe:2.3:a:amazon:opensearch:*:*:*:*:*:-:*:*

part: a version: * update: *

VendorAmazon (0ed129a9-8e26-53dc-aefe-55957e638c30)
ProductOpensearch (60deea36-77e2-58d2-ac81-20f3c88c0043)
Edition*
Language*
Software edition*
Target software-
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:gem/opensearch-ruby purl2cpe 2026-06-01 10:12:11.828477
pkg:github/opensearch-project/opensearch-ruby purl2cpe 2026-06-01 10:12:11.828479

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-23613 vulnerable 2026-06-08 05:56:03.776796 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
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-23612 vulnerable 2026-06-08 05:56:03.776156 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
Reference links
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.