How severe is GHSA-jh6x-7xfg-9cq2?

GHSA-jh6x-7xfg-9cq2 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-jh6x-7xfg-9cq2?

GHSA-jh6x-7xfg-9cq2 affects the following packages: org.opencastproject:opencast-elasticsearch-impl (Maven), org.opencastproject:opencast-elasticsearch-impl (Maven), org.opencastproject:opencast-elasticsearch-impl (Maven). Ecosystems affected: Maven.

How do I fix GHSA-jh6x-7xfg-9cq2?

Update org.opencastproject:opencast-elasticsearch-impl to 13.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jh6x-7xfg-9cq2 is resolved across your whole dependency graph.

How do I detect GHSA-jh6x-7xfg-9cq2 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opencastproject:opencast-elasticsearch-impl. 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-jh6x-7xfg-9cq2 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-jh6x-7xfg-9cq2?

O3 pinpoints whether GHSA-jh6x-7xfg-9cq2 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-jh6x-7xfg-9cq2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jh6x-7xfg-9cq2 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.

What is the EPSS score for GHSA-jh6x-7xfg-9cq2?

GHSA-jh6x-7xfg-9cq2 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 55th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-jh6x-7xfg-9cq2?

GHSA-jh6x-7xfg-9cq2 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jh6x-7xfg-9cq2 published, and has it been updated?

GHSA-jh6x-7xfg-9cq2 was published on November 20, 2024 and was last updated on October 28, 2025. 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-jh6x-7xfg-9cq2

MEDIUM

Searching Opencast may cause a denial of service

Also known asCVE-2024-52797

Published

Nov 20, 2024

Updated

Oct 28, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk55th percentile+0.61%

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

3 pkgs affected

☕org.opencastproject:opencast-elasticsearch-impl☕org.opencastproject:opencast-elasticsearch-impl☕org.opencastproject:opencast-elasticsearch-impl

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

First noticed in Opencast 13 and 14, Opencast's Elasticsearch integration may generate syntactically invalid Elasticsearch queries in relation to previously acceptable search queries. From Opencast version 11.4 and newer, Elasticsearch queries are retried a configurable number of times in the case of error to handle temporary losses of connection to Elasticsearch. These invalid queries would fail, causing the retry mechanism to begin requerying with the same syntactically invalid query immediately, in an infinite loop. This causes a massive increase in log size which can in some cases cause a denial of service due to disk exhaustion.

Patches

Opencast 13.10 and Opencast 14.3 contain patches (https://github.com/opencast/opencast/pull/5150, and https://github.com/opencast/opencast/pull/5033) which address the base issue, with Opencast 16.7 containing changes which harmonize the search behaviour between the admin UI and external API. Users are strongly recommended to upgrade as soon as possible if running versions prior to 13.10 or 14.3. While the relevant endpoints require (by default) ROLE_ADMIN or ROLE_API_SERIES_VIEW, the problem queries are otherwise innocuous. This issue could be easily triggered by normal administrative work on an affected Opencast system. If you are running a version newer than 13.10 and 14.3 and seeing different results when searching in your admin UI vs your external API or LMS, upgrading to 16.7 should resolve the issue.

Workarounds

None identified.

References

Pull Requests

Preventing the infinite loop issue: https://github.com/opencast/opencast/pull/5150
Sanitizing user input: https://github.com/opencast/opencast/pull/5033

If you have any questions or comments about this advisory:

Open an issue in our issue tracker Email us at [email protected]

Credit

Credit to Adilagha Aliyev of Graz University of Technology, Educational Technologies, [email protected]

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.opencastproject:opencast-elasticsearch-impl`	≥ 11.4&&< 13.10	13.10
☕Maven	`org.opencastproject:opencast-elasticsearch-impl`	≥ 14.0&&< 14.3	14.3
☕Maven	`org.opencastproject:opencast-elasticsearch-impl`	≥ 15.0&&< 16.7	16.7

Detection & mitigation playbook

Open-source dependency

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

Frequently Asked Questions

### Impact First noticed in Opencast 13 and 14, Opencast's Elasticsearch integration may generate syntactically invalid Elasticsearch queries in relation to previously acceptable search queries. From Opencast version 11.4 and newer, Elasticsearch queries are retried a configurable number of times in the case of error to handle temporary losses of connection to Elasticsearch. These invalid queries would fail, causing the retry mechanism to begin requerying with the same syntactically invalid query immediately, in an infinite loop. This causes a massive increase in log size which can in some

O3 Security · Impact-Aware SCA

Is GHSA-jh6x-7xfg-9cq2 in your dependencies?

O3 detects GHSA-jh6x-7xfg-9cq2 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

GHSA-jh6x-7xfg-9cq2

EPSS Exploitation Probability

Blast Radius

Description

Impact

Patches

Workarounds

References

If you have any questions or comments about this advisory:

Credit

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-jh6x-7xfg-9cq2 in your dependencies?