CVE-2020-5222 Hard-Coded Key Used For Remember-me Token in OpenCast

Medium 6.8 Published Updated

Attackers can reuse remember-me tokens across servers due to a hard-coded key, allowing unauthorized access without credentials.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2020-5222?

CVE-2020-5222 is a medium-severity vulnerability in opencast, published on 30 Jan 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official 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

Weakness: CWE-798

Which versions are affected by CVE-2020-5222?

4 open source packages ship an affected version, including org.opencastproject:opencast-kernel. It affects 1 product.

PackageAffectedFixed in
org.opencastproject:opencast-kernel MavenAll versions7.6
org.opencastproject:opencast-kernel MavenAll versions7.6
org.opencastproject:opencast-kernel MavenFrom 8.08.1
org.opencastproject:opencast-kernel MavenFrom 8.08.1

Products include Apereo Opencast.

How do I fix CVE-2020-5222?

Upgrade org.opencastproject:opencast-kernel to a fixed version for your release line: 7.6 or 8.1.

Is CVE-2020-5222 being exploited?

There is no known exploitation of CVE-2020-5222 in the wild and no public exploit code.

Sources

Also known as GHSA-mh8g-hprg-8363.

Is CVE-2020-5222 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free