CVE-2020-5229
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N
Summary
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.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| opencast | opencast | < 8.1 | affected |
Weaknesses
- CWE-327: CWE-327: Use of a Broken or Risky Cryptographic Algorithm
ADP Enrichment
CVE Program Container
Additional References
- https://github.com/opencast/opencast/security/advisories/GHSA-h362-m8f2-5x7c
- https://github.com/opencast/opencast/commit/32bfbe5f78e214e2d589f92050228b91d704758e
References
- https://github.com/opencast/opencast/security/advisories/GHSA-h362-m8f2-5x7c
- https://github.com/opencast/opencast/commit/32bfbe5f78e214e2d589f92050228b91d704758e
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.