CVE-2020-5229

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 users 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.

Risk Information

Base Score

8.1

MODERATE

Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS Score

Exploitation Probability

0.153

Associated Vulnerability

Vulnerability	OS Platform
Vulnerabilities CVE-2020-5229 are fixed in Opencast-Project-opencast-common-jpa-impl 7.6	Windows
Vulnerabilities CVE-2020-5229 are fixed in Opencast-Project-opencast-common-jpa-impl 8.1	Windows
Vulnerabilities CVE-2020-5229 are fixed in Opencast-Project-opencast-common-jpa-impl for Linux 7.6	Linux
Vulnerabilities CVE-2020-5229 are fixed in Opencast-Project-opencast-common-jpa-impl for Linux 8.1	Linux

Patch Details

No records found

References

https://nvd.nist.gov/vuln/detail/CVE-2023-1234
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1234