Opencast up to 8.0 Password Hashing md5.json MD5 risky encryption

Summaryinfo

A vulnerability has been found in Opencast up to 8.0 and classified as critical. Affected by this issue is some unknown functionality of the file /user-utils/users/md5.json of the component Password Hashing. The manipulation leads to risky encryption (MD5). This vulnerability is traded as CVE-2020-5229. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Opencast up to 8.0. It has been rated as problematic. This issue affects an unknown part of the file /user-utils/users/md5.json of the component Password Hashing. The manipulation with an unknown input leads to a risky encryption vulnerability (MD5). Using CWE to declare the problem leads to CWE-327. The product uses a broken or risky cryptographic algorithm or protocol. Impacted is confidentiality. The summary by CVE is:

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.

The weakness was shared 01/30/2020 (GitHub Repository). It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2020-5229 since 01/02/2020. The exploitation is known to be difficult. The attack may be initiated remotely. A simple authentication is necessary for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.

By approaching the search of inurl:user-utils/users/md5.json it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 8.1 eliminates this vulnerability.

The entries VDB-149581, VDB-149580, VDB-149578 and VDB-149577 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Opencast

Version

• 8.0

License

• open-source

Website

• Product: https://github.com/opencast/opencast/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion