Vulnerability in org.opencastproject:base (CVE-2020-5230)
Summary
Vulnerability in org.opencastproject:base (CVE-2020-5230). Data can be tampered with by attackers. Mitigation: upgrade to 8.1 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-5230 has been found in org.opencastproject:base.
Data can be tampered with by attackers.
What to do: upgrade org.opencastproject:base to 8.1 or later.
If unsure, ask your IT team or search "org.opencastproject:base CVE-2020-5230" on the vendor's site.
CVE-2020-5230 (org.opencastproject:base) — CWE-99
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 8.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-99) exists in org.opencastproject:base.
Check the vendor advisory for the affected versions of org.opencastproject:base.
Severity: ?. Data can be tampered with by attackers.
Update to 8.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.opencastproject:base を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.opencastproject:base to 8.1ステージング環境で 8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- patch github.com