ghsa-jh6x-7xfg-9cq2
Vulnerability from github
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 security@opencast.org
Credit
Credit to Adilagha Aliyev of Graz University of Technology, Educational Technologies, adilagha.aliyev@gmail.com
{ "affected": [ { "package": { "ecosystem": "Maven", "name": "org.opencastproject:opencast-elasticsearch-impl" }, "ranges": [ { "events": [ { "introduced": "11.4" }, { "fixed": "13.10" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Maven", "name": "org.opencastproject:opencast-elasticsearch-impl" }, "ranges": [ { "events": [ { "introduced": "14.0" }, { "fixed": "14.3" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Maven", "name": "org.opencastproject:opencast-elasticsearch-impl" }, "ranges": [ { "events": [ { "introduced": "15.0" }, { "last_affected": "16.6" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2024-52797" ], "database_specific": { "cwe_ids": [ "CWE-770" ], "github_reviewed": true, "github_reviewed_at": "2024-11-20T22:46:53Z", "nvd_published_at": null, "severity": "MODERATE" }, "details": "### Impact\nFirst noticed in Opencast 13 and 14, Opencast\u0027s 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.\n\n### Patches\nOpencast 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.\n\n### Workarounds\nNone identified.\n\n### References\nPull Requests\n- Preventing the infinite loop issue: https://github.com/opencast/opencast/pull/5150\n- Sanitizing user input: https://github.com/opencast/opencast/pull/5033\n\n### If you have any questions or comments about this advisory:\nOpen an issue in [our issue tracker](https://github.com/opencast/opencast/issues)\nEmail us at [security@opencast.org](mailto:security@opencast.org)\n\n### Credit\nCredit to Adilagha Aliyev of Graz University of Technology, Educational Technologies, adilagha.aliyev@gmail.com", "id": "GHSA-jh6x-7xfg-9cq2", "modified": "2024-11-21T01:30:21Z", "published": "2024-11-20T22:46:53Z", "references": [ { "type": "WEB", "url": "https://github.com/opencast/opencast/security/advisories/GHSA-jh6x-7xfg-9cq2" }, { "type": "WEB", "url": "https://github.com/opencast/opencast/pull/5033" }, { "type": "WEB", "url": "https://github.com/opencast/opencast/pull/5150" }, { "type": "PACKAGE", "url": "https://github.com/opencast/opencast" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ], "summary": "Searching Opencast may cause a denial of service" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.