# GHSA-2rh5-jvgx-pgw3: Any storage file can be downloaded from p.sh if full server path is known

> Attackers can download any storage file if the full server path is known, bypassing content read access controls in the default configuration.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2021

## What is GHSA-2rh5-jvgx-pgw3?

GHSA-2rh5-jvgx-pgw3 is a missing authorization vulnerability in ezsystems/ezplatform, published on 14 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by GHSA-2rh5-jvgx-pgw3?

4 open source packages ship an affected version, including ezsystems/ezplatform.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ezsystems/ezplatform` | Packagist | All versions | 1.13.6.1 |
| `ezsystems/ezplatform` | Packagist | All versions | 1.13.6.1 |
| `ezsystems/ezplatform` | Packagist | From 2.0.0 | 2.5.24.1 |
| `ezsystems/ezplatform` | Packagist | From 2.0.0 | 2.5.24.1 |

## How do I fix GHSA-2rh5-jvgx-pgw3?

Upgrade ezsystems/ezplatform to a fixed version for your release line: 1.13.6.1 or 2.5.24.1.

## Is GHSA-2rh5-jvgx-pgw3 being exploited?

There is no known exploitation of GHSA-2rh5-jvgx-pgw3 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2rh5-jvgx-pgw3 and fix it if it is affected.

What it is: GHSA-2rh5-jvgx-pgw3 is a missing authorization vulnerability in ezsystems/ezplatform, published on 14 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-2rh5-jvgx-pgw3 in the wild and no public exploit code.

Affected packages and fixed versions:
- ezsystems/ezplatform (Packagist): affected all versions; fixed in 1.13.6.1
- ezsystems/ezplatform (Packagist): affected all versions; fixed in 1.13.6.1
- ezsystems/ezplatform (Packagist): affected from 2.0.0; fixed in 2.5.24.1
- ezsystems/ezplatform (Packagist): affected from 2.0.0; fixed in 2.5.24.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-2rh5-jvgx-pgw3/ (Markdown: https://insights.sbomify.com/GHSA-2rh5-jvgx-pgw3/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2rh5-jvgx-pgw3

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2rh5-jvgx-pgw3/
Summaries are generated and may contain mistakes; the official description above is the record.