Login timing attack in ibexa/core
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 software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Composer package | ibexa/core | >= 4.0.0, < 4.0.7, >= 4.1.0, < 4.1.4 | 4.0.7, 4.1.4 |
References
- Weakness (CWE)
CWE-208- Platform
- Composer
- Package
ibexa/core- Disclosed
- 02.06.2022
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-2x4v-g8cx-jxrq - CC BY 4.0
Vulnerability history: ibexa/core
All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 5
- First → latest
- 04.2022 03.2024
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 3
- Medium 1
- Low 1
Disclosures per year
- 2022: 3
- 2023: 1
- 2024: 1
- 2025: 0
- 2026: 0
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.