Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
MEDIUM severity

GHSA-3393-hvrj-w7v3

MEDIUM

GHSA-3393-hvrj-w7v3 is a medium-severity (CVSS 5.7) CWE-674 vulnerability in org.elasticsearch:elasticsearch. O3 Security confirms whether GHSA-3393-hvrj-w7v3 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Denial of Service in Elasticsearch

Also known asBIT-elasticsearch-2021-22144CVE-2021-22144
Published
Aug 9, 2021
Updated
Feb 20, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Feb 20, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
org.elasticsearch:elasticsearchorg.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

In Elasticsearch versions before 7.13.3 and 6.8.17 an uncontrolled recursion vulnerability that could lead to a denial of service attack was identified in the Elasticsearch Grok parser. A user with the ability to submit arbitrary queries to Elasticsearch could create a malicious Grok query that will crash the Elasticsearch node.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.elasticsearch:elasticsearchall versions6.8.17
Mavenorg.elasticsearch:elasticsearch7.0.0-alpha1&&< 7.13.37.13.3

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    Update org.elasticsearch:elasticsearch to 6.8.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3393-hvrj-w7v3 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-3393-hvrj-w7v3 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-3393-hvrj-w7v3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Elasticsearch versions before 7.13.3 and 6.8.17 an uncontrolled recursion vulnerability that could lead to a denial of service attack was identified in the Elasticsearch Grok parser. A user with the ability to submit arbitrary queries to Elasticsearch could create a malicious Grok query that will crash the Elasticsearch node.
O3 Security · Impact-Aware SCA

Is GHSA-3393-hvrj-w7v3 in your dependencies?

O3 detects GHSA-3393-hvrj-w7v3 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.