eZ Publish Legacy Patch EZSA-2018-001 for Several vulnerabilitiesGHSA-82rv-45pc-v28w
Fix: ezsystems/ezpublish-legacy@6db0e6bGHSA-82rv-45pc-v28w is a security vulnerability in ezsystems/ezpublish-legacy. A fix is available for ezsystems/ezpublish-legacy — see the affected versions and patch details below.
Real-World Exposure
ezsystems/ezpublish-legacy🐘ezsystems/ezpublish-legacy🐘ezsystems/ezpublish-legacyReal-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
This security advisory fixes 4 separate vulnerabilities in eZ Publish Legacy, and we recommend that you install it as soon as possible if you are using Legacy by itself or via the LegacyBridge.
First, it increases the randomness, and thus the security, of the pseudo-random bytes used to generate a hash for the "forgot password" feature. This protects accounts against being taken over through attacks trying to predict the hash. If the increased randomness is not available in your PHP installation, it will now log a warning.
Second, it improves security of the information collector feature, by ensuring no collection emails will be sent from invalid manipulated forms.
Third, it stops the possible leaking of the names of content objects that should not be readable for certain users, on installations where these users can create or edit XML text.
Fourth, it protects against cross-site scripting (XSS) in the Matrix data type, on installations where users are allowed to edit content classes / content types.
We recommend that you install the security update as soon as possible.
To install, use Composer to update to one of the "Resolving versions" mentioned above, or apply these patches manually: https://github.com/ezsystems/ezpublish-legacy/commit/917711eb7ffe2b52a3e9fe12505f6810a63696f7 https://github.com/ezsystems/ezpublish-legacy/commit/6db0e6b7739481f27d954548388bd3f0ed2c6fdd https://github.com/ezsystems/ezpublish-legacy/commit/efcd2b61b15eaaf74e0ff28d6c723cf28e655dab https://github.com/ezsystems/ezpublish-legacy/commit/f9ffaf590b63b4f552142cfd4441afbbfb3f19b1
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | ezsystems/ezpublish-legacy | ≥ 2011.0.0&&< 2017.12.2.1 | 2017.12.2.1composer require ezsystems/ezpublish-legacy:^2017.12.2.1 |
| 🐘Packagist | ezsystems/ezpublish-legacy | ≥ 5.4.0&&< 5.4.11.3 | 5.4.11.3composer require ezsystems/ezpublish-legacy:^5.4.11.3 |
| 🐘Packagist | ezsystems/ezpublish-legacy | ≥ 5.3.0&&< 5.3.12.3 | 5.3.12.3composer require ezsystems/ezpublish-legacy:^5.3.12.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezpublish-legacy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ezsystems/ezpublish-legacy to 2017.12.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-82rv-45pc-v28w is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-82rv-45pc-v28w in your dependencies?
Find it across Packagist, including transitive dependencies.