---
id: CVE-2024-6832
title: >-
  The account locking mechanism fails to trigger when secondary user stores are
  inaccessible
summary: >-
  The account locking mechanism fails to trigger when secondary user stores are
  inaccessible. The software does not maintain a consistent state for account
  locking if it cannot reach all configured user stores, allowing an attacker to
  repe…
severity: medium
cvss: 5.9
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'
cwe:
  - CWE-693
vendor: wso2
product: api_control_plane
affected:
  - api_control_plane = 4.5.0
  - api_control_plane = 4.6.0
  - api_manager = 3.1.0
  - api_manager = 3.2.0
  - api_manager = 3.2.1
  - api_manager = 4.1.0
  - api_manager = 4.2.0
  - api_manager = 4.3.0
  - api_manager = 4.4.0
  - api_manager = 4.5.0
  - api_manager = 4.6.0
  - identity_server = 5.10.0
  - identity_server = 5.11.0
  - identity_server = 6.0.0
  - identity_server = 6.1.0
  - identity_server = 7.0.0
  - identity_server_as_key_manager = 5.10.0
  - open_banking_am = 2.0.0
  - open_banking_iam = 2.0.0
  - traffic_manager = 4.5.0
  - traffic_manager = 4.6.0
  - universal_gateway = 4.5.0
  - universal_gateway = 4.6.0
published: '2026-08-06'
updated: '2026-08-09'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2024-6832'
references:
  - url: >-
      https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3352/
    label: ed10eef1-636d-4fbe-9993-6890dfa878f8
tags:
  - nvd
epss: 0.00241
epssPercentile: 0.15479
ingestedAt: '2026-08-09T14:33:32.087Z'
---

## Overview

The account locking mechanism fails to trigger when secondary user stores are inaccessible. The software does not maintain a consistent state for account locking if it cannot reach all configured user stores, allowing an attacker to repeatedly attempt authentication with invalid credentials without triggering the lockout mechanism for users within active stores.

When the account locking mechanism is bypassed due to the inaccessibility of secondary user stores, users in accessible user stores are left vulnerable to brute force attacks. A malicious actor can exploit this by attempting numerous invalid password combinations against a user account without the expected account lockout consequence.

## Affected

- `api_control_plane = 4.5.0`
- `api_control_plane = 4.6.0`
- `api_manager = 3.1.0`
- `api_manager = 3.2.0`
- `api_manager = 3.2.1`
- `api_manager = 4.1.0`
- `api_manager = 4.2.0`
- `api_manager = 4.3.0`
- `api_manager = 4.4.0`
- `api_manager = 4.5.0`
- `api_manager = 4.6.0`
- `identity_server = 5.10.0`
- `identity_server = 5.11.0`
- `identity_server = 6.0.0`
- `identity_server = 6.1.0`
- `identity_server = 7.0.0`
- `identity_server_as_key_manager = 5.10.0`
- `open_banking_am = 2.0.0`
- `open_banking_iam = 2.0.0`
- `traffic_manager = 4.5.0`
- `traffic_manager = 4.6.0`
- `universal_gateway = 4.5.0`
- `universal_gateway = 4.6.0`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.