A vulnerability identified in NetIQ Advance Authentication that doesnt enforce account lockout when brute force attack is performed on API based login. This issue may lead to user account compromise if successful or may impact server performance. This issue impacts all NetIQ Advance Authentication before 6.3.5.1
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Netiq_advanced_authentication | Microfocus | * | 6.3 (excluding) |
| Netiq_advanced_authentication | Microfocus | 6.3 (including) | 6.3 (including) |
| Netiq_advanced_authentication | Microfocus | 6.3-sp1 (including) | 6.3-sp1 (including) |
| Netiq_advanced_authentication | Microfocus | 6.3-sp2 (including) | 6.3-sp2 (including) |
| Netiq_advanced_authentication | Microfocus | 6.3-sp3 (including) | 6.3-sp3 (including) |
| Netiq_advanced_authentication | Microfocus | 6.3-sp4 (including) | 6.3-sp4 (including) |
| Netiq_advanced_authentication | Microfocus | 6.3-sp4_patch1 (including) | 6.3-sp4_patch1 (including) |
| Netiq_advanced_authentication | Microfocus | 6.3-sp5 (including) | 6.3-sp5 (including) |
Locking is a type of synchronization behavior that ensures that multiple independently-operating processes or threads do not interfere with each other when accessing the same resource. All processes/threads are expected to follow the same steps for locking. If these steps are not followed precisely - or if no locking is done at all - then another process/thread could modify the shared resource in a way that is not visible or predictable to the original process. This can lead to data or memory corruption, denial of service, etc.