What is GHSA-6G3J-P5G6-992F?

GHSA-6G3J-P5G6-992F is a medium-severity security vulnerability in org.opensearch:opensearch (maven), affecting versions < 1.3.14. It is fixed in 1.3.14, 2.11.1.

How severe is GHSA-6G3J-P5G6-992F?

GHSA-6G3J-P5G6-992F has a CVSS score of 6.5 (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.

Which versions of org.opensearch:opensearch are affected by GHSA-6G3J-P5G6-992F?

org.opensearch:opensearch (maven) versions < 1.3.14 is affected.

Is there a fix for GHSA-6G3J-P5G6-992F?

Yes. GHSA-6G3J-P5G6-992F is fixed in 1.3.14, 2.11.1. Upgrade to this version or later.

Is GHSA-6G3J-P5G6-992F exploitable, and should I be worried?

Whether GHSA-6G3J-P5G6-992F 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.

What actually determines whether GHSA-6G3J-P5G6-992F 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.

GHSA-6G3J-P5G6-992F in org.opensearch:opensearch

Q: How severe is GHSA-6G3J-P5G6-992F?

GHSA-6G3J-P5G6-992F has a CVSS score of 6.5 (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.

Q: Which versions of org.opensearch:opensearch are affected by GHSA-6G3J-P5G6-992F?

org.opensearch:opensearch (maven) versions < 1.3.14 is affected.

Q: Is there a fix for GHSA-6G3J-P5G6-992F?

Yes. GHSA-6G3J-P5G6-992F is fixed in 1.3.14, 2.11.1. Upgrade to this version or later.

Q: Is GHSA-6G3J-P5G6-992F exploitable, and should I be worried?

Whether GHSA-6G3J-P5G6-992F 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.

Q: What actually determines whether GHSA-6G3J-P5G6-992F 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.

Q: How do I fix GHSA-6G3J-P5G6-992F?

Upgrade: org.opensearch:opensearch to 1.3.14 or later, org.opensearch:opensearch to 2.11.1 or later.

Summary

OpenSearch StackOverflow vulnerability

Mitigation

Versions 1.3.14 and 2.11.1 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 [email protected]. Please do not create a public GitHub issue.

Impact

A flaw was discovered in OpenSearch, affecting the _search API that allowed a specially crafted query string to cause a Stack Overflow and ultimately a Denial of Service.

The issue was identified by Elastic Engineering and corresponds to security advisory ESA-2023-14 (CVE-2023-31419).

GHSA-6G3J-P5G6-992F has a CVSS score of 6.5 (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 (1.3.14, 2.11.1); upgrading removes the vulnerable code path.

Affected versions

org.opensearch:opensearch (< 1.3.14) org.opensearch:opensearch (>= 2.0.0, < 2.11.1)

Security releases

org.opensearch:opensearch → 1.3.14 (maven) org.opensearch:opensearch → 2.11.1 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.opensearch:opensearch to 1.3.14 or later; org.opensearch:opensearch to 2.11.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-6G3J-P5G6-992F? GHSA-6G3J-P5G6-992F is a medium-severity security vulnerability in org.opensearch:opensearch (maven), affecting versions < 1.3.14. It is fixed in 1.3.14, 2.11.1.
How severe is GHSA-6G3J-P5G6-992F? GHSA-6G3J-P5G6-992F has a CVSS score of 6.5 (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.
Which versions of org.opensearch:opensearch are affected by GHSA-6G3J-P5G6-992F? org.opensearch:opensearch (maven) versions < 1.3.14 is affected.
Is there a fix for GHSA-6G3J-P5G6-992F? Yes. GHSA-6G3J-P5G6-992F is fixed in 1.3.14, 2.11.1. Upgrade to this version or later.
Is GHSA-6G3J-P5G6-992F exploitable, and should I be worried? Whether GHSA-6G3J-P5G6-992F 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
What actually determines whether GHSA-6G3J-P5G6-992F 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.
How do I fix GHSA-6G3J-P5G6-992F?
- Upgrade org.opensearch:opensearch to 1.3.14 or later
- Upgrade org.opensearch:opensearch to 2.11.1 or later