CVE-2020-5230 json
Opencast uses unsafe identifiers
published 2020-01-30 6 y ago modified 2026-07-08 4 mo ago also GHSA-w29m-fjp4-qhmq , EUVD-2020-0279
- cvss
- 7.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
Opencast before 8.1 and 7.6 allows almost arbitrary identifiers for media packages and elements to be used. This can be problematic for operation and security since such identifiers are sometimes used for file system operations which may lead to an attacker being able to escape working directories and write files to other locations. In addition, Opencast's Id.toString(…) vs Id.compact(…) behavior, the latter trying to mitigate some of the file system problems, can cause errors due to identifier mismatch since an identifier may unintentionally change. This issue is fixed in Opencast 7.6 and 8.1.
Patch / fix
- maven org.opencastproject:base 7.6, 8.1
- apereo opencast 7.6
Exploit prediction
1.17% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.opencastproject:base | <7.6 >=8.0, <8.1 |
7.6 8.1 |
Affected products
- opencast opencast
Classification
References
-
github.com
/opencast/opencast/commit/bbb473f34ab95497d6c432c81285efb0c739f317
web, patch
-
github.com
/opencast/opencast/security/advisories/GHSA-w29m-fjp4-qhmq
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-5230
advisory
Sources
- CVE List CVE-2020-5230
- GitHub Advisory GHSA-w29m-fjp4-qhmq
- NVD CVE-2020-5230
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.