GHSA-2rh5-jvgx-pgw3 — ezsystems/ezplatform
GHSA-2rh5-jvgx-pgw3 is a security vulnerability in ezsystems/ezplatform. A fix is available for ezsystems/ezplatform — see the affected versions and patch details below.
Any storage file can be downloaded from p.sh if full server path is known
Real-World Exposure
ezsystems/ezplatform🐘ezsystems/ezplatformReal-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
The default configuration for platform.sh (.platform.app.yaml) allows access to uploaded files if you know or can guess their location, regardless of whether roles grant content read access to the content containing those files. If you're using Legacy Bridge, the default configuration also allows access to certain legacy files that should not be readable, including the legacy var directory and extension directories.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | ezsystems/ezplatform | ≥ 2.0.0&&< 2.5.24.1 | 2.5.24.1composer require ezsystems/ezplatform:^2.5.24.1 |
| 🐘Packagist | ezsystems/ezplatform | all versions | 1.13.6.1composer require ezsystems/ezplatform:^1.13.6.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezplatform, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ezsystems/ezplatform to 2.5.24.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2rh5-jvgx-pgw3 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-2rh5-jvgx-pgw3 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2rh5-jvgx-pgw3. 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-2rh5-jvgx-pgw3 in your dependencies?
O3 Security finds GHSA-2rh5-jvgx-pgw3 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.