Description
Opencast before 8.1 stores passwords using the rather outdated and cryptographically insecure MD5 hash algorithm. Furthermore, the hashes are salted using the username instead of a random salt, causing hashes for users with the same username and password to collide which is problematic especially for popular users like the default `admin` user. This essentially means that for an attacker, it might be feasible to reconstruct a user's password given access to these hashes. Note that attackers needing access to the hashes means that they must gain access to the database in which these are stored first to be able to start cracking the passwords. The problem is addressed in Opencast 8.1 which now uses the modern and much stronger bcrypt password hashing algorithm for storing passwords. Note, that old hashes remain MD5 until the password is updated. For a list of users whose password hashes are stored using MD5, take a look at the `/user-utils/users/md5.json` REST endpoint.
Remediation
References
https://github.com/opencast/opencast/commit/32bfbe5f78e214e2d589f92050228b91d704758e
https://github.com/opencast/opencast/security/advisories/GHSA-h362-m8f2-5x7c
Related Vulnerabilities
CVE-2022-24794 Vulnerability in npm package express-openid-connect
CVE-2020-13949 Vulnerability in maven package org.apache.thrift:libthrift
CVE-2014-0193 Vulnerability in maven package org.onosproject:onlab-stc
CVE-2021-43861 Vulnerability in npm package mermaid
CVE-2022-24881 Vulnerability in maven package com.hccake:ballcat-codegen