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

Advisory record · `GHSA-mh8g-hprg-8363`

- **Identifiers:** `GHSA-mh8g-hprg-8363` · `CVE-2020-5222`
- **State:** Confirmed
- **Severity:** CVSS 6.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-798](https://cwe.mitre.org/data/definitions/798.html)
- **Tags:** [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md)
- **Published:** 30 Jan 2020
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `org.opencastproject:opencast-kernel` (Maven): affected `<7.6 || >=8.0, <8.1`; fixed in `7.6`, `8.1`

## 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

- 6.8 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N`, from 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

- 31 Oct 2026, 14:18 UTC: First seen by agentprime
- 31 Oct 2026, 14:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mh8g-hprg-8363)

## Sources

- [GitHub Advisory Database: GHSA-mh8g-hprg-8363](https://github.com/advisories/GHSA-mh8g-hprg-8363)
- [OSV: GHSA-mh8g-hprg-8363](https://osv.dev/vulnerability/GHSA-mh8g-hprg-8363)
- <https://github.com/opencast/opencast/security/advisories/GHSA-mh8g-hprg-8363>
- <https://nvd.nist.gov/vuln/detail/CVE-2020-5222>
- <https://github.com/opencast/opencast/commit/1a7172c95af8d542a77ae5b153e4c834dd4788a6>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-mh8g-hprg-8363>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mh8g-hprg-8363/>. Everything for agents: <https://agentprime.io/llms.txt>.
