CVE-2020-5229

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.

CVSS v3 8.1 HIGH
CVSS v2.0 5.5 MEDIUM

8.1^/10

CVSS v3 : HIGH

Vector :

Exploitability : 2.8 / Impact : 5.2

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact NONE

Scope UNCHANGED

5.5^/10

CVSS v2.0 : MEDIUM

Vector : AV:N/AC:L/Au:S/C:P/I:P/A:N

Exploitability : 8.0 / Impact : 4.9

Access Vector NETWORK

Access Complexity LOW

Authentication SINGLE

Confidentiality Impact PARTIAL

Integrity Impact PARTIAL

Availability Impact NONE

References

Link	Resource
https://github.com/opencast/opencast/commit/32bfbe5f78e214e2d589f92050228b91d704758e	Patch
https://github.com/opencast/opencast/security/advisories/GHSA-h362-m8f2-5x7c	Third Party Advisory

Configurations

Configuration 1 (hide)

cpe:2.3:a:apereo:opencast:*:*:*:*:*:*:*:*

History

No history.

Information

Published : 2020-01-30 20:15

Updated : 2024-02-04 20:39

NVD link : CVE-2020-5229

Mitre link : CVE-2020-5229

CVE.ORG link : CVE-2020-5229

JSON object : View

Products Affected

apereo

opencast

CWE

CWE-327

Use of a Broken or Risky Cryptographic Algorithm

{"id": "CVE-2020-5229", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 5.5, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:S/C:P/I:P/A:N", "authentication": "SINGLE", "integrityImpact": "PARTIAL", "accessComplexity": "LOW", "availabilityImpact": "NONE", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 4.9, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 8.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.1, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 2.8}, {"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 7.7, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.8, "exploitabilityScore": 1.3}]}, "published": "2020-01-30T20:15:10.420", "references": [{"url": "https://github.com/opencast/opencast/commit/32bfbe5f78e214e2d589f92050228b91d704758e", "tags": ["Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/opencast/opencast/security/advisories/GHSA-h362-m8f2-5x7c", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-327"}]}, {"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-327"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Opencast versiones anteriores a 8.1, almacena contrase\u00f1as usando el algoritmo hash MD5 bastante antiguo y criptogr\u00e1ficamente no seguro. Adem\u00e1s, los hash son salados utilizando el nombre de usuario en lugar de una sal aleatoria, causando que los hash para usuarios con el mismo nombre de usuario y contrase\u00f1a choquen, lo que es problem\u00e1tico, especialmente para usuarios populares tales como el usuario predeterminado \"admin\". Esto esencialmente significa que para un atacante, podr\u00eda ser factible reconstruir la contrase\u00f1a de un usuario dado el acceso a estos hashes. Considere que los atacantes al necesitar acceso a los hashes significa que deben obtener acceso a la base de datos en la que se almacenan primero, para que sean capaces de descifrar las contrase\u00f1as. El problema es abordado en Opencast versi\u00f3n 8.1, que ahora utiliza el algoritmo de hash de contrase\u00f1a bcrypt moderno y mucho m\u00e1s fuerte para almacenar contrase\u00f1as. Tome en cuenta que los hashes antiguos permanecen MD5 hasta que se actualiza la contrase\u00f1a. Para obtener una lista de los usuarios cuyos hash de contrase\u00f1a son almacenados con MD5, visualice al endpoint REST \"/user-utils/users/md5.json\"."}], "lastModified": "2020-02-05T20:52:42.963", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:apereo:opencast:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "11673AEB-4E7B-43BF-98BA-9031E47794ED", "versionEndExcluding": "8.1"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}