Files Accessible to External Parties in Opencast
Published Dec 14, 2021 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
Files Accessible to External Parties in Opencast
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
Opencast before version 10.6 allows references to local file URLs in ingested media packages, allowing attackers to include local files from Opencast's host machines and making them available via the web interface.
Potential impact
Before Opencast 10.6, Opencast would open and include local files during ingests. Attackers could exploit this to include most local files the process has read access to, extracting secrets from the host machine. For example, to expose the custom.properties of develop.opencast.org via the asset manager, an attacker could have run: An attacker would need to have the privileges required to add new media to exploit this. But these are often widely given.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Dec 14, 2021 · Last refreshed Nov 3, 2026