How severe is GHSA-8wx3-324g-w4qq?

GHSA-8wx3-324g-w4qq has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-8wx3-324g-w4qq?

GHSA-8wx3-324g-w4qq affects the following packages: org.opensearch.plugin:opensearch-security (Maven), org.opensearch.plugin:opensearch-security (Maven). Ecosystems affected: Maven.

How do I fix GHSA-8wx3-324g-w4qq?

Update org.opensearch.plugin:opensearch-security to 1.3.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8wx3-324g-w4qq is resolved across your whole dependency graph.

How do I detect GHSA-8wx3-324g-w4qq in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opensearch.plugin:opensearch-security. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-8wx3-324g-w4qq if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-8wx3-324g-w4qq?

O3 pinpoints whether GHSA-8wx3-324g-w4qq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-8wx3-324g-w4qq actively exploited in the wild?

No public exploit code has been indexed for GHSA-8wx3-324g-w4qq yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-8wx3-324g-w4qq published, and has it been updated?

GHSA-8wx3-324g-w4qq was published on October 17, 2023 and was last updated on December 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-8wx3-324g-w4qq

HIGH

OpenSearch uncontrolled resource consumption

Published

Oct 17, 2023

Updated

Dec 4, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

☕org.opensearch.plugin:opensearch-security☕org.opensearch.plugin:opensearch-security

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

An issue has been identified with how OpenSearch handled incoming requests on the HTTP layer. An unauthenticated user could force an OpenSearch node to exit with an OutOfMemory error by sending a moderate number of malformed HTTP requests.

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

Mitigation

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.opensearch.plugin:opensearch-security`	all versions	1.3.14.0
☕Maven	`org.opensearch.plugin:opensearch-security`	≥ 2.0.0.0&&< 2.11.0.0	2.11.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opensearch.plugin:opensearch-security. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.opensearch.plugin:opensearch-security to 1.3.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8wx3-324g-w4qq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-8wx3-324g-w4qq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8wx3-324g-w4qq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact An issue has been identified with how OpenSearch handled incoming requests on the HTTP layer. An unauthenticated user could force an OpenSearch node to exit with an OutOfMemory error by sending a moderate number of malformed HTTP requests. The issue was identified by Elastic Engineering and corresponds to security advisory [ESA-2023-13](https://discuss.elastic.co/t/elasticsearch-8-9-0-7-17-13-security-update/343616) (CVE-2023-31418). ### Mitigation Versions 1.3.14 and 2.11.0 contain a fix for this issue. ### For more information If you have any questions or comments about this ad

O3 Security · Impact-Aware SCA

Is GHSA-8wx3-324g-w4qq in your dependencies?

O3 detects GHSA-8wx3-324g-w4qq across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works