GHSA-22VX-2X23-98W6

Description

A flaw was identified in the OpenSearch Security plugin's handling of index rollover requests. When a rollover request included an explicit target index name, the security plugin did not properly evaluate access control permissions against the target index. This could allow a user with rollover permissions on a source index to create a new index with a name they are not authorized to use.

Workarounds

Grant the indices:admin/rollover permission only to fully trusted users.

A user with indices:admin/rollover permission on a source index pattern could roll over to a target index name outside their authorized index patterns. This is limited to index creation via the rollover API and requires the user to already have rollover privileges on the source index.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

GHSA-22VX-2X23-98W6 has a CVSS score of 2.2 (Low). The vector is network-reachable, high 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.19.4.0, 3.2.0.0); upgrading removes the vulnerable code path.

Kodem intelligence

This issue is fixed in OpenSearch 2.19.4 and 3.2.0

1. What is GHSA-22VX-2X23-98W6? GHSA-22VX-2X23-98W6 is a low-severity incorrect authorization vulnerability in org.opensearch.plugin:opensearch-security (maven), affecting versions >= 1.0.0, <= 2.19.3. It is fixed in 2.19.4.0, 3.2.0.0. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is GHSA-22VX-2X23-98W6? GHSA-22VX-2X23-98W6 has a CVSS score of 2.2 (Low). 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 GHSA-22VX-2X23-98W6? org.opensearch.plugin:opensearch-security (maven) versions >= 1.0.0, <= 2.19.3 is affected.
4. Is there a fix for GHSA-22VX-2X23-98W6? Yes. GHSA-22VX-2X23-98W6 is fixed in 2.19.4.0, 3.2.0.0. Upgrade to this version or later.
5. Is GHSA-22VX-2X23-98W6 exploitable, and should I be worried? Whether GHSA-22VX-2X23-98W6 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 GHSA-22VX-2X23-98W6 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 GHSA-22VX-2X23-98W6?
   • Upgrade org.opensearch.plugin:opensearch-security to 2.19.4.0 or later
   • Upgrade org.opensearch.plugin:opensearch-security to 3.2.0.0 or later

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