Opencast hat eine partielle Path Traversal Schwachstelle in der UI Konfiguration.

The vulnerability stems from insufficient checks against path traversal attacks within the UI configuration module. Specifically, the path is validated without properly checking for file separators, enabling an attacker to potentially access files located in adjacent directories that share a common path prefix. For example, if the default UI configuration directory is /etc/opencast/ui-config, an attacker could gain access to files within a directory like /etc/opencast/ui-config-hidden, provided those files are readable by the Opencast process. While general path traversal is not possible, the potential for unauthorized file access within the Opencast environment poses a risk to sensitive configuration data or other files stored in adjacent directories.

Organizations deploying OpenCast for video management and streaming, particularly those using legacy configurations or shared hosting environments, are at risk. Systems with default directory structures and permissive file permissions are especially vulnerable.

• linux / server:

find /etc/opencast/ui-config/ -type f -perm -o -r -print0 | xargs -0 ls -l | grep -i 'ui-config-hidden'

• java / server: Monitor OpenCast application logs for unusual file access attempts or errors related to path traversal. Look for patterns indicating attempts to access files outside the expected configuration directory. • generic web: Examine web server access logs for requests targeting the UI configuration endpoint with unusual path parameters. Look for attempts to manipulate the path to access files outside the intended directory.

1. 2025-08-29Disclosure

   disclosure

1. Reserviert2025-08-08
2. Veröffentlicht2025-08-29
3. EPSS aktualisiert2026-03-23

The primary mitigation for CVE-2025-55202 is to upgrade OpenCast UI configuration to version 17.7 or later, which includes the necessary fix. If an immediate upgrade is not feasible, consider implementing stricter file permissions on the /etc/opencast/ui-config directory and any adjacent directories containing sensitive data. Ensure that only the Opencast process has read access to these files. While a WAF or proxy rule is unlikely to be effective for this specific vulnerability, reviewing and hardening the overall Opencast deployment is recommended. After upgrading, verify the fix by attempting to access a file outside the intended UI configuration directory using a crafted request; access should be denied.