GHSA-59g4-hpg3-3gcp is a critical-severity (CVSS 9.9) CWE-552 vulnerability in org.opencastproject:opencast-ingest-service-impl. 3 public exploit references exist, so weaponization risk is real. A fix is available for org.opencastproject:opencast-ingest-service-impl — see the affected versions and patch details below.
Files Accessible to External Parties in Opencast
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-59g4-hpg3-3gcp plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.opencastproject:opencast-ingest-service-implReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
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:
curl -f -i -u admin:opencast \
https://develop.opencast.org/ingest/addMediaPackage/fast \
-F 'flavor=presenter/source'\
-F mediaUri=file:///srv/opencast/opencast-dist-allinone/etc/custom.properties\
-F title="custom.properties"
An attacker would need to have the privileges required to add new media to exploit this. But these are often widely given.
Patches
The issue has been fixed in Opencast 10.6 and 11.0.
Workarounds
You can mitigate this issue by narrowing down the read access Opencast has to files on the file system using UNIX permissions or mandatory access control systems like SELinux. This cannot prevent access to files Opencast needs to read though and we highly recommend updating.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in our issue tracker
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.opencastproject:opencast-ingest-service-impl | all versions | 10.6org.opencastproject:opencast-ingest-service-impl:10.6 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opencastproject:opencast-ingest-service-impl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.opencastproject:opencast-ingest-service-impl to 10.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-59g4-hpg3-3gcp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-59g4-hpg3-3gcp can be triaged on real exposure rather than presence alone.
Tailored to GHSA-59g4-hpg3-3gcp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-59g4-hpg3-3gcp in your dependencies?
O3 Security finds GHSA-59g4-hpg3-3gcp across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.