CVE-2020-5222

Hard-Coded Key Used For Remember-me Token in OpenCast

Description

Opencast before 7.6 and 8.1 enables a remember-me cookie based on a hash created from the username, password, and an additional system key. This means that an attacker getting access to a remember-me token for one server can get access to all servers which allow log-in using the same credentials without ever needing the credentials. This problem is fixed in Opencast 7.6 and Opencast 8.1

Category

6.8
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.26%
Third-Party Advisory github.com
Affected: opencast opencast
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2020-5222?
CVE-2020-5222 has been scored as a medium severity vulnerability.
How to fix CVE-2020-5222?
To fix CVE-2020-5222, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-5222 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-5222 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-5222?
CVE-2020-5222 affects opencast opencast.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.