Advisory record · GHSA-mh8g-hprg-8363

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

CVSS 6.8 MediumEPSS 0.0094 · 61st percentile

Published by the GitHub Advisory Database at 30 Jan 2020, 21:21 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.opencastproject:opencast-kernelMaven<7.6 || >=8.0, <8.17.6, 8.1
Identifiers
GHSA-mh8g-hprg-8363 · CVE-2020-5222
Weakness (CWE)
CWE-798
Published
30 Jan 2020
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Opencast (org.opencastproject:opencast-kernel) versions before 7.6 and from 8.0 before 8.1 use a hard-coded key for the remember-me cookie, so every installation shares the same key. An attacker who obtains a remember-me token from one server can use it on other servers that accept the same credentials, without knowing the login details. Upgrade to 7.6 or 8.1. For older versions, set a custom remember-me key in the security configuration file for each server.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.8 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0094, the 61st percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:18 UTC First seen by agentprime
  2. 31 Oct 2026, 14:18 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.