GHSA-JH6X-7XFG-9CQ2

Vulnerability from github – Published: 2024-11-20 22:46 – Updated: 2025-10-28 19:47
VLAI
Summary
Searching Opencast may cause a denial of service
Details

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

Severity
6.5 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Show details on source website
To clipboard 

{
  "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"
        }
      ]
    },
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 16.6"
      },
      "package": {
        "ecosystem": "Maven",
        "name": "org.opencastproject:opencast-elasticsearch-impl"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "15.0"
            },
            {
              "fixed": "16.7"
            }
          ],
          "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": "2024-11-21T11:15:35Z",
    "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": "2025-10-28T19:47:39Z",
  "published": "2024-11-20T22:46:53Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/opencast/opencast/security/advisories/GHSA-jh6x-7xfg-9cq2"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-52797"
    },
    {
      "type": "WEB",
      "url": "https://github.com/opencast/opencast/pull/5033"
    },
    {
      "type": "WEB",
      "url": "https://github.com/opencast/opencast/pull/5150"
    },
    {
      "type": "WEB",
      "url": "https://github.com/opencast/opencast/commit/3d5ebd163674eb18e070f52b64a18f92188f98c3"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/opencast/opencast"
    },
    {
      "type": "WEB",
      "url": "https://github.com/opencast/opencast/blob/7ad05f72814f057130122904015d471cfe5f4c58/docs/guides/admin/docs/changelog/older-versions/opencast-16.md?plain=1#L74"
    }
  ],
  "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"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.