GHSA-vf5j-r2hw-2hrw
HIGHOpenCloud Affected by Public Link Exploit
Blast Radius
github.com/opencloud-eu/opencloud🐹github.com/opencloud-eu/opencloudReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
A security issue was discovered in Reva that enables a malicious user to bypass the scope validation of a public link. That allows it to access resources outside the scope of a public link.
OpenCloud uses Reva as one of its core components and thus it is affected.
Patches
Update to OpenCloud version >= 4.0.3 (stable release) Update to OpenCloud version >= 5.0.2 (rolling release)
Workarounds
If projects are unable to update immediately, please implement the following security configuration to disable public link shares temporarily until the final solution for this problem is rolled out.
Configuration Adjustment
- Docker Compose: Edit the docker-compose.yml and add
GATEWAY_STORAGE_PUBLIC_LINK_ENDPOINT=“”(empty string value) in theenvironmentsection of theopencloudcontainer.
Verification of Mitigation
Execute the following test:
- Create a public link for testing.
- Open the link url in a private (no active login) browser tab.
- An error page with “unknown error” will be displayed.
This configuration provides immediate protection and should be implemented immediately. Configuration mitigation is available. It mitigates the problem completely.
For more information
If there are questions or comments about this advisory:
- Security Support: [email protected]
- Technical Support: [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/opencloud-eu/opencloud | ≥ 4.0.0&&< 4.0.3 | 4.0.3 |
| 🐹Go | github.com/opencloud-eu/opencloud | ≥ 5.0.0&&< 5.0.2 | 5.0.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/opencloud-eu/opencloud. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/opencloud-eu/opencloud to 4.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vf5j-r2hw-2hrw 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 pinpoints whether GHSA-vf5j-r2hw-2hrw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-vf5j-r2hw-2hrw. 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-vf5j-r2hw-2hrw in your dependencies?
O3 detects GHSA-vf5j-r2hw-2hrw across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.