How severe is GHSA-qwrx-45xf-jjf7?

GHSA-qwrx-45xf-jjf7 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-qwrx-45xf-jjf7?

GHSA-qwrx-45xf-jjf7 affects the following packages: org.elasticsearch:elasticsearch (Maven), org.elasticsearch:elasticsearch (Maven). Ecosystems affected: Maven.

How do I fix GHSA-qwrx-45xf-jjf7?

Update org.elasticsearch:elasticsearch to 7.17.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qwrx-45xf-jjf7 is resolved across your whole dependency graph.

How do I detect GHSA-qwrx-45xf-jjf7 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.elasticsearch:elasticsearch. 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-qwrx-45xf-jjf7 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-qwrx-45xf-jjf7?

O3 pinpoints whether GHSA-qwrx-45xf-jjf7 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-qwrx-45xf-jjf7 actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-qwrx-45xf-jjf7, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-qwrx-45xf-jjf7?

GHSA-qwrx-45xf-jjf7 has an EPSS (Exploit Prediction Scoring System) score of 60.7%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-qwrx-45xf-jjf7?

GHSA-qwrx-45xf-jjf7 is classified as CWE-121 (CWE-121), Out-of-bounds Write (CWE-787). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-qwrx-45xf-jjf7 published, and has it been updated?

GHSA-qwrx-45xf-jjf7 was published on October 26, 2023 and was last updated on February 22, 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-qwrx-45xf-jjf7

MEDIUM

Elasticsearch vulnerable to stack overflow in the search API

Also known asBIT-elasticsearch-2023-31419CVE-2023-31419

Published

Oct 26, 2023

Updated

Feb 22, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

60.7%probability of exploitation in next 30 days

High Risk99th percentile+21.47%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

☕org.elasticsearch:elasticsearch☕org.elasticsearch:elasticsearch

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

A flaw was discovered in Elasticsearch affecting the _search API that allowed a specially crafted query string to cause a stack overflow and ultimately a denial of service.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.elasticsearch:elasticsearch`	≥ 7.0.0&&< 7.17.13	7.17.13
☕Maven	`org.elasticsearch:elasticsearch`	≥ 8.0.0&&< 8.9.1	8.9.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A flaw was discovered in Elasticsearch, affecting the _search API that a…

github.comGithubSep 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.elasticsearch:elasticsearch. 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.elasticsearch:elasticsearch to 7.17.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qwrx-45xf-jjf7 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-qwrx-45xf-jjf7 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-qwrx-45xf-jjf7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A flaw was discovered in Elasticsearch affecting the `_search` API that allowed a specially crafted query string to cause a stack overflow and ultimately a denial of service.

O3 Security · Impact-Aware SCA

Is GHSA-qwrx-45xf-jjf7 in your dependencies?

O3 detects GHSA-qwrx-45xf-jjf7 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