How severe is CVE-2024-52797?

CVE-2024-52797 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 CVE-2024-52797?

CVE-2024-52797 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 CVE-2024-52797?

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 CVE-2024-52797 is resolved across your whole dependency graph.

How do I detect CVE-2024-52797 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-52797 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2024-52797 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-52797 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 CVE-2024-52797?

CVE-2024-52797 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 60th 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 CVE-2024-52797?

CVE-2024-52797 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 CVE-2024-52797 published, and has it been updated?

CVE-2024-52797 was published on November 21, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2024-52797 — opencast-elasticsearch-im…

MEDIUMFix: opencast/opencast@3d5ebd1

CVE-2024-52797 is a medium-severity (CVSS 6.5) CWE-770 vulnerability in org.opencastproject:opencast-elasticsearch-impl. A fix is available for org.opencastproject:opencast-elasticsearch-impl — see the affected versions and patch details below.

Searching Opencast may cause a denial of service

Also known asGHSA-jh6x-7xfg-9cq2

Published

Nov 21, 2024

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-52797.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

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`org.opencastproject:opencast-elasticsearch-impl:13.10`
☕Maven	`org.opencastproject:opencast-elasticsearch-impl`	≥ 14.0&&< 14.3	14.3`org.opencastproject:opencast-elasticsearch-impl:14.3`
☕Maven	`org.opencastproject:opencast-elasticsearch-impl`	≥ 15.0&&< 16.7	16.7`org.opencastproject:opencast-elasticsearch-impl:16.7`

Affected Products

1 product · 3 configurations

Application

opencastapereo

≥ 15.0 && < 16.7

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2024-52797 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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