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

Not scored Published

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

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

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.

PackageAffectedFixed in
ezsystems/ezplatform PackagistAll versions1.13.6.1
ezsystems/ezplatform PackagistAll versions1.13.6.1
ezsystems/ezplatform PackagistFrom 2.0.02.5.24.1
ezsystems/ezplatform PackagistFrom 2.0.02.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.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

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.

Sources

Is GHSA-2rh5-jvgx-pgw3 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free