CVE-2023-23612
highpriority · track · 35EPSS 0.008 · 56 %ileEURUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 4.7–8.8
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (9)
Products and version ranges known to be affected.
- Maven org.opensearch.plugin:opensearch-security< 1.3.8osvUSpkg:maven/org.opensearch.plugin/opensearch-security
- Maven org.opensearch.plugin:opensearch-security2.0.0 → 2.5.0osvUSpkg:maven/org.opensearch.plugin/opensearch-security
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-864v-6qj7-62qjIssue with whitespace in JWT roles in OpenSearch2023-01-24ghsa · osvUS
### Advisory title: Issue with whitespace in JWT roles ### Affected versions: OpenSearch 1.0.0-1.3.7 and 2.0.0-2.4.1 ### Patched versions: OpenSearch 1.3.8 and 2.5.0 ### Impact: 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. ### Patches: OpenSearch versions 1.3.8 and 2.5.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 [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.
also known as (4)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (7)
External citations — patches, advisories, analysis.
- https://cxsecurity.com/cveshow/CVE-2023-23612/cnnvd
- https://github.com/opensearch-project/OpenSearch/releases/tag/2.5.0cnnvd
- https://github.com/opensearch-project/security/security/advisories/GHSA-864v-6qj7-62qjcnnvd
- https://github.com/opensearch-project/OpenSearch/releases/tag/2.5.0enisa_euvd
- https://github.com/opensearch-project/security/security/advisories/GHSA-864v-6qj7-62qjenisa_euvd
- https://github.com/opensearch-project/OpenSearch/releases/tag/2.5.0Third Party Advisorynvd
- https://github.com/opensearch-project/security/security/advisories/GHSA-864v-6qj7-62qjThird Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan