Timing attack in eZ Platform IbexaGHSA-66m4-gc8h-hpjx
LOWGHSA-66m4-gc8h-hpjx is a low-severity (CVSS 3.7) CWE-362 vulnerability in ezsystems/ezplatform-kernel. A fix is available for ezsystems/ezplatform-kernel — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-66m4-gc8h-hpjx.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
ezsystems/ezplatform-kernel🐘ezsystems/ezpublish-kernelReal-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
Ibexa DXP is using random execution time to hinder timing attacks against user accounts, a method of discovering whether a given account exists in a system without knowing its password, thus affecting privacy. This implementation was found to not be good enough in some situations. The fix replaces this with constant time functionality, configured in the new security.yml parameter 'ibexa.security.authentication.constant_auth_time'. It will log a warning if the constant time is exceeded. If this happens the setting should be increased.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | ezsystems/ezplatform-kernel | ≥ 1.3.0&&< 1.3.19 | 1.3.19composer require ezsystems/ezplatform-kernel:^1.3.19 |
| 🐘Packagist | ezsystems/ezpublish-kernel | ≥ 7.5.0&&< 7.5.29 | 7.5.29composer require ezsystems/ezpublish-kernel:^7.5.29 |
Affected Products
commerceibexadigital experience platformibexaez platformibexaez platform kernelibexaezplatform-page-builderibexajmspaymentcorebundleibexaDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezplatform-kernel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ezsystems/ezplatform-kernel to 1.3.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-66m4-gc8h-hpjx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-66m4-gc8h-hpjx in your dependencies?
Find it across Packagist, including transitive dependencies.