Skip to content
Fencer Intel
high —

GHSA-2rh5-jvgx-pgw3 json

Any storage file can be downloaded from p.sh if full server path is known

published 5y ago modified last yr.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist ezsystems/ezplatform 1.13.6.1, 2.5.24.1

Is GHSA-2rh5-jvgx-pgw3 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
packagist ezsystems/ezplatform
>=2.0.0, <2.5.24.1
<1.13.6.1
2.5.24.1
1.13.6.1

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.