Login timing attack in ibexa/core
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-208.
Summary
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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | ibexa/core (Packagist) | 4.0.0 to before 4.0.7 | 4.0.7 | Patch available | GHSA-2x4v-g8cx-jxrq |
| — | ibexa/core (Packagist) | 4.1.0 to before 4.1.4 | 4.1.4 | Patch available | GHSA-2x4v-g8cx-jxrq |
- ibexa/core (Packagist) Vendor— Affected 4.0.0 to before 4.0.7 Fixed in 4.0.7 Patch available GHSA-2x4v-g8cx-jxrq
- ibexa/core (Packagist) Vendor— Affected 4.1.0 to before 4.1.4 Fixed in 4.1.4 Patch available GHSA-2x4v-g8cx-jxrq
Remediation
- Fix · GHSA-2x4v-g8cx-jxrq ibexa/core (Packagist) Fixed in 4.0.7 Advisory →
- Fix · GHSA-2x4v-g8cx-jxrq ibexa/core (Packagist) Fixed in 4.1.4 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-2x4v-g8cx-jxrq
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences