CVE-2022-48366

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.

Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing. Typical impact: TOCTOU exploits, data corruption, or privilege escalation.

CVE-2022-48366 has a CVSS score of 3.7 (Low). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.3.19, 7.5.29); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2022-48366? CVE-2022-48366 is a low-severity race condition vulnerability in ezsystems/ezplatform-kernel (composer), affecting versions >= 1.3.0, < 1.3.19. It is fixed in 1.3.19, 7.5.29. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.
2. How severe is CVE-2022-48366? CVE-2022-48366 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2022-48366?
   • ezsystems/ezplatform-kernel (composer) (versions >= 1.3.0, < 1.3.19)
   • ezsystems/ezpublish-kernel (composer) (versions >= 7.5.0, < 7.5.29)
4. Is there a fix for CVE-2022-48366? Yes. CVE-2022-48366 is fixed in 1.3.19, 7.5.29. Upgrade to this version or later.
5. Is CVE-2022-48366 exploitable, and should I be worried? Whether CVE-2022-48366 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-48366 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-48366?
   • Upgrade ezsystems/ezplatform-kernel to 1.3.19 or later
   • Upgrade ezsystems/ezpublish-kernel to 7.5.29 or later