GHSA-gv2c-5g79-h73c — ezsystems/ezplatform-kern…
Fix: ezsystems/ezplatform-kernel@affa252GHSA-gv2c-5g79-h73c is a security vulnerability in ezsystems/ezplatform-kernel. A fix is available for ezsystems/ezplatform-kernel — see the affected versions and patch details below.
Ibexa ezplatform-kernel download route allows filename change
Real-World Exposure
ezsystems/ezplatform-kernelReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The route used for file downloads allows specifying the name of the downloaded file. This is an unintended side effect of the implementation, and means one could construct download URLs with filenames that have no relation to the actual file, which could lead to misunderstandings and confusion, and possibly other harm. As such it is a low severity vulnerability. It affects all supported versions of Ibexa DXP and eZ Platform, in installations where downloadable files exist.
Patches
The issue is fixed in all supported versions of ezsystems/ezplatform-kernel, see "Patched versions". An advisory is also published for ezsystems/ezpublish-kernel and ibexa/core, please see those repositories. Commit: https://github.com/ezsystems/ezplatform-kernel/commit/affa2520e5e986e477ca7f7c93b9ca2c30188063
Workarounds
None, other than blocking all downloads.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | ezsystems/ezplatform-kernel | ≥ 1.3.0&&< 1.3.34 | 1.3.34composer require ezsystems/ezplatform-kernel:^1.3.34 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezplatform-kernel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ezsystems/ezplatform-kernel to 1.3.34 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gv2c-5g79-h73c 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-gv2c-5g79-h73c can be triaged on real exposure rather than presence alone.
Tailored to GHSA-gv2c-5g79-h73c. 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-gv2c-5g79-h73c in your dependencies?
O3 Security finds GHSA-gv2c-5g79-h73c across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.