CVE-2020-5222

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

<sec:remember-me key="CUSTOM_RANDOM_KEY" user-service-ref="userDetailsService" />

The security configuration in etc/security/mh_default_org.xml enables a remember-me cookie based on a hash created from the username, password, and an additional system key. Opencast has hard-coded this system key in the large XML file and never mentions to change this, basically ensuring that all systems use the same key:

<sec:remember-me key="opencast" user-service-ref="userDetailsService" />

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. For example, a remember-me token obtained from develop.opencast.org can be used on stable.opencast.org without actually knowing the log-in credentials.

Such an attack will usually not work on different installations, assuming that safe, unique passwords are used, but it is basically guaranteed to work to get access to all machines of one cluster if a token from one machine is compromised.

Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact. Typical impact: unauthorized access using the static credential.

CVE-2020-5222 has a CVSS score of 6.8 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.6, 8.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

This problem is fixed in Opencast 7.6 and Opencast 8.1

1. What is CVE-2020-5222? CVE-2020-5222 is a medium-severity use of hard-coded credentials vulnerability in org.opencastproject:opencast-kernel (maven), affecting versions < 7.6. It is fixed in 7.6, 8.1. Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact.
2. How severe is CVE-2020-5222? CVE-2020-5222 has a CVSS score of 6.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.opencastproject:opencast-kernel are affected by CVE-2020-5222? org.opencastproject:opencast-kernel (maven) versions < 7.6 is affected.
4. Is there a fix for CVE-2020-5222? Yes. CVE-2020-5222 is fixed in 7.6, 8.1. Upgrade to this version or later.
5. Is CVE-2020-5222 exploitable, and should I be worried? Whether CVE-2020-5222 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2020-5222 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2020-5222?
   • Upgrade org.opencastproject:opencast-kernel to 7.6 or later
   • Upgrade org.opencastproject:opencast-kernel to 8.1 or later

Other vulnerabilities in org.opencastproject:opencast-kernel