How severe is GHSA-hq8m-v68g-8cf8?

No CVSS score has been assigned to GHSA-hq8m-v68g-8cf8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hq8m-v68g-8cf8?

GHSA-hq8m-v68g-8cf8 affects the following packages: org.opencastproject:opencast-user-interface-configuration (Maven), org.opencastproject:opencast-user-interface-configuration (Maven). Ecosystems affected: Maven.

How do I fix GHSA-hq8m-v68g-8cf8?

Update org.opencastproject:opencast-user-interface-configuration to 17.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hq8m-v68g-8cf8 is resolved across your whole dependency graph.

How do I detect GHSA-hq8m-v68g-8cf8 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opencastproject:opencast-user-interface-configuration. 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-hq8m-v68g-8cf8 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-hq8m-v68g-8cf8?

O3 pinpoints whether GHSA-hq8m-v68g-8cf8 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-hq8m-v68g-8cf8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-hq8m-v68g-8cf8 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-hq8m-v68g-8cf8?

GHSA-hq8m-v68g-8cf8 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 28th 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.

When was GHSA-hq8m-v68g-8cf8 published, and has it been updated?

GHSA-hq8m-v68g-8cf8 was published on August 29, 2025 and was last updated on August 29, 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-hq8m-v68g-8cf8

Opencast has a partial path traversal vulnerability in UI config

Also known asCVE-2025-55202

Published

Aug 29, 2025

Updated

Aug 29, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk28th percentile+0.24%

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

2 pkgs affected

☕org.opencastproject:opencast-user-interface-configuration☕org.opencastproject:opencast-user-interface-configuration

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

The protections against path traversal attacks in the UI config module are insufficient, still partially allowing for attacks in very specific cases.

The path is checked without checking for the file separator. This could allow attackers access to files within another folder which starts with the same path. For example, the default UI config directory is placed at /etc/opencast/ui-config. Without this patch, an attacker can get access to files in a folder /etc/opencast/ui-config-hidden if those files are readable by Opencast.

General path traversal is not possible. For example, an attacker cannot exploit this to access files in /etc/opencast/encoding or even in /etc/opencast/ directly.

How dangerous is this?

Theoretically, this vulnerability may be exploited to get access to some non-public files. However, given the default structure of Opencast's configuration, this is extremely unlikely to hit any users. There can be but one ui-config folders. This makes it quite unlikely for any user to have created an additional folder starting with ui-config. Users could also rename this folder, but since there is no real reason for anyone to do this, this, again is extremely unlikely to trigger this issue.

How to fix the issue

To mitigate this, check if you have folders which start with the same path as your ui-config folder
A fix is available in https://github.com/opencast/opencast/pull/6979
Updating to Opencast 17.7 or 18.1 will fix the issue

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.opencastproject:opencast-user-interface-configuration`	all versions	17.7
☕Maven	`org.opencastproject:opencast-user-interface-configuration`	≥ 18.0&&< 18.1	18.1

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-user-interface-configuration. 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-user-interface-configuration to 17.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hq8m-v68g-8cf8 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-hq8m-v68g-8cf8 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-hq8m-v68g-8cf8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The protections against path traversal attacks in the UI config module are insufficient, still partially allowing for attacks in very specific cases. The path is checked without checking for the file separator. This could allow attackers access to files within another folder which starts with the same path. For example, the default UI config directory is placed at `/etc/opencast/ui-config`. Without this patch, an attacker can get access to files in a folder `/etc/opencast/ui-config-hidden` if those files are readable by Opencast. General path traversal is not possible. For example, an attack

O3 Security · Impact-Aware SCA

Is GHSA-hq8m-v68g-8cf8 in your dependencies?

O3 detects GHSA-hq8m-v68g-8cf8 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