WSO2 Enterprise Integrator: Protection Mechanism Failure
CVE-2024-6832 is a high-severity protection mechanism failure vulnerability in WSO2 Enterprise Integrator from WSO2, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 6.6.0.229 as the first without the flaw, so updating WSO2 Enterprise Integrator to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.41% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update WSO2 Enterprise Integrator to 6.6.0.229 or a later version.
- Update WSO2 API Control Plane to 4.5.0.40 or 4.6.0.4 or 4.6.0.5, whichever matches your release line, or a later version.
- Update WSO2 Traffic Manager to 4.5.0.38 or 4.6.0.4 or 4.6.0.5, whichever matches your release line, or a later version.
- Read the advisory on security.docs.wso2.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| WSO2 | WSO2 Enterprise Integrator | 6.6.0 up to, but not including, 6.6.0.229 | 6.6.0.229 |
| WSO2 | WSO2 API Control Plane | 4.5.0 up to, but not including, 4.5.0.40; 4.6.0 up to, but not including, 4.6.0.4; 4.6.0 up to, but not including, 4.6.0.5 | 4.5.0.40, 4.6.0.4, 4.6.0.5 |
| WSO2 | WSO2 Traffic Manager | 4.5.0 up to, but not including, 4.5.0.38; 4.6.0 up to, but not including, 4.6.0.4; 4.6.0 up to, but not including, 4.6.0.5 | 4.5.0.38, 4.6.0.4, 4.6.0.5 |
| WSO2 | WSO2 Universal Gateway | 4.5.0 up to, but not including, 4.5.0.38; 4.6.0 up to, but not including, 4.6.0.4; 4.6.0 up to, but not including, 4.6.0.5 | 4.5.0.38, 4.6.0.4, 4.6.0.5 |
| WSO2 | WSO2 API Manager | 3.1.0 up to, but not including, 3.1.0.296; 3.2.0 up to, but not including, 3.2.0.386; 3.2.0 up to, but not including, 3.2.0.455; 3.2.1 up to, but not including, 3.2.1.74; 4.1.0 up to, but not including, 4.1.0.238; 4.2.0 up to, but not including, 4.2.0.179; 4.3.0 up to, but not including, 4.3.0.91; 4.4.0 up to, but not including, 4.4.0.55; and 2 more ranges | 3.1.0.296, 3.2.0.386, 3.2.0.455, 3.2.1.74, 4.1.0.238, 4.2.0.179 |
| WSO2 | WSO2 Identity Server | 5.10.0 up to, but not including, 5.10.0.320; 5.11.0 up to, but not including, 5.11.0.427; 6.0.0 up to, but not including, 6.0.0.254; 6.1.0 up to, but not including, 6.1.0.195; 7.0.0 up to, but not including, 7.0.0.82 | 5.10.0.320, 5.11.0.427, 6.0.0.254, 6.1.0.195, 7.0.0.82 |
| WSO2 | WSO2 Identity Server as Key Manager | 5.10.0 up to, but not including, 5.10.0.314 | 5.10.0.314 |
| WSO2 | WSO2 Open Banking IAM | 2.0.0 up to, but not including, 2.0.0.366 | 2.0.0.366 |
| WSO2 | WSO2 Open Banking AM | 2.0.0 up to, but not including, 2.0.0.345 | 2.0.0.345 |
| WSO2 | WSO2 Carbon User Manager Kernel | 4.5.0 up to, but not including, 4.5.0.7; 4.5.3 up to, but not including, 4.5.3.53; 4.6.0 up to, but not including, 4.6.0.196; 4.6.1 up to, but not including, 4.6.1.163; 4.6.1 up to, but not including, 4.6.1.164; 4.6.3 up to, but not including, 4.6.3.44; 4.6.4 up to, but not including, 4.6.4.25; 4.7.1 up to, but not including, 4.7.1.77; and 7 more ranges | 4.5.0.7, 4.5.3.53, 4.6.0.196, 4.6.1.163, 4.6.1.164, 4.6.3.44 |
| WSO2 | API Control Plane | 4.5.0; 4.6.0 | Not stated |
| WSO2 | API Manager | 3.1.0; 3.2.0; 3.2.1; 4.1.0; 4.2.0; 4.3.0; 4.4.0; 4.5.0; and 1 more ranges | Not stated |
| WSO2 | Identity Server | 5.10.0; 5.11.0; 6.0.0; 6.1.0; 7.0.0 | Not stated |
| WSO2 | Identity Server As Key Manager | 5.10.0 | Not stated |
| WSO2 | Open Banking Am | 2.0.0 | Not stated |
| WSO2 | Open Banking Iam | 2.0.0 | Not stated |
| WSO2 | Traffic Manager | 4.5.0; 4.6.0 | Not stated |
| WSO2 | Universal Gateway | 4.5.0; 4.6.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 5.9 | Medium | CNA |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Protection Mechanism Failure
The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in WSO2 Enterprise Integrator
- 9.1 Critical severity
- 8.8 High severity
- 7.2 High severity
- 7.2 High severity
- 9.1 Critical severity
- 7.2 High severity
Recent Protection Mechanism Failure vulnerabilities
- 8.8 High severity
- 8.3 High severity
- 8.8 High severity
- 9.4 Critical severity
- 7.2 High severity
- 7.5 High severity
Spotted an error? Tell us.