GHSA-83X9-VC3C-HGHC

Description

A flaw was identified in the OpenSearch REST layer that could allow authorization checks to be bypassed when processing certain malformed HTTP requests. This could permit unauthorized access to restricted API endpoints in environments that rely on REST-layer authorization.

Transport-level authorization is not affected by this issue.

The default OpenSearch distribution is not affected by this issue. REST actions in the default distribution have corresponding transport actions that independently enforce authorization. Custom plugins that register REST actions without a corresponding transport action may be affected, potentially allowing unauthorized read access to those endpoints.

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-83X9-VC3C-HGHC has a CVSS score of 3.7 (Low). The vector is network-reachable, no 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.0.0); upgrading removes the vulnerable code path.

Kodem intelligence

This issue is fixed in OpenSearch 2.19.0. Users should upgrade to 2.19.0 or later.

1. What is GHSA-83X9-VC3C-HGHC? GHSA-83X9-VC3C-HGHC is a low-severity incorrect authorization vulnerability in org.opensearch.plugin:opensearch-security (maven), affecting versions >= 2.11.0.0, < 2.19.0.0. It is fixed in 2.19.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-83X9-VC3C-HGHC? GHSA-83X9-VC3C-HGHC has a CVSS score of 3.7 (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-83X9-VC3C-HGHC? org.opensearch.plugin:opensearch-security (maven) versions >= 2.11.0.0, < 2.19.0.0 is affected.
4. Is there a fix for GHSA-83X9-VC3C-HGHC? Yes. GHSA-83X9-VC3C-HGHC is fixed in 2.19.0.0. Upgrade to this version or later.
5. Is GHSA-83X9-VC3C-HGHC exploitable, and should I be worried? Whether GHSA-83X9-VC3C-HGHC 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-83X9-VC3C-HGHC 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-83X9-VC3C-HGHC? Upgrade org.opensearch.plugin:opensearch-security to 2.19.0.0 or later.

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