GHSA-X83W-23JP-G6PW

Description

A flaw was identified in the OpenSearch Security plugin's document-level security (DLS) implementation. DLS restrictions were not correctly applied to search queries that use has_parent or has_child join relations. This could allow an authenticated user to access document contents that should have been restricted by DLS rules.

Workarounds

Avoid using the join field type on indices that are subject to DLS rules.

An authenticated user with access to an index containing parent/child join relations could bypass DLS restrictions on documents linked by those relations, potentially accessing restricted document contents. This only affects clusters that use both DLS and the join field type on the same 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-X83W-23JP-G6PW has a CVSS score of 5.3 (Medium). The vector is network-reachable, low 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-X83W-23JP-G6PW? GHSA-X83W-23JP-G6PW is a medium-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-X83W-23JP-G6PW? GHSA-X83W-23JP-G6PW has a CVSS score of 5.3 (Medium). 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-X83W-23JP-G6PW? org.opensearch.plugin:opensearch-security (maven) versions >= 1.0.0, <= 2.19.3 is affected.
4. Is there a fix for GHSA-X83W-23JP-G6PW? Yes. GHSA-X83W-23JP-G6PW is fixed in 2.19.4.0, 3.2.0.0. Upgrade to this version or later.
5. Is GHSA-X83W-23JP-G6PW exploitable, and should I be worried? Whether GHSA-X83W-23JP-G6PW 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-X83W-23JP-G6PW 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-X83W-23JP-G6PW?
   • 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