GHSA-gv2c-5g79-h73c json
Ibexa ezplatform-kernel download route allows filename change
published 3y 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
### 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 https://developers.ibexa.co/security-advisories/ibexa-sa-2023-005-vulnerabilities-in-solr-search-and-file-downloads
Patch / fix
Is GHSA-gv2c-5g79-h73c 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 FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | ezsystems/ezplatform-kernel | >=1.3.0, <1.3.34 |
1.3.34 |
References
-
github.com
/ezsystems/ezplatform-kernel/commit/affa2520e5e986e477ca7f7c93b9ca2c30188063
web
-
github.com
/ezsystems/ezplatform-kernel/security/advisories/GHSA-gv2c-5g79-h73c
web
-
developers.ibexa.co
/security-advisories/ibexa-sa-2023-005-vulnerabilities-in-solr-search-and-file-downloads
web
-
github.com
/ezsystems/ezplatform-kernel
package
Sources
- GitHub Advisory GHSA-gv2c-5g79-h73c
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.