CVE-2020-5222

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

HIGH
8.8
CVSS Score
Published: January 30, 2020 at 08:50 PM UTC
Updated: June 17, 2026 at 03:21 AM UTC
2 products affected across 2 vendorsOpencastOpencast

Using opencast by opencast?

Get instant alerts when new vulnerabilities affect opencast - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.9%

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 7.68.0
Affected range stops below 7.6, so it looks safe — our inference, not a vendor statement
v < 7.6v < 8.1
Affected range stops below 7.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-798

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card