Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
CVE-2022-48366
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. This issue is in ezsystems/ezpublish-kernel 7.5.x prior to 7.5.29, ibexa/core 4.0.x prior to 4.0.7, 4.1.x prior to 4.1.4 and ezsystems/ezplatform-kernel 1.3.x prior to 1.3.19.
- HIGH
- NETWORK
- NONE
- UNCHANGED
- NONE
- NONE
- LOW
- NONE
CWE-362 - Race Condition
A race condition occurs in a shared memory program when two threads/processes access the same shared memory data, and at least one thread executes a write operation. This vulnerability manipulates the time to check vs. time to use (TOC/TOU) gap between the threads in the critical section to cause disorientation in the shared data. The impact can vary from compromising the confidentiality of the system to causing the system to crash or to execute arbitrary code.
Advisory Timeline
- Published
