CVE-2024-6832

HIGHCVSS 7.5/10EPSS 0.25%

Last modified

CVE-2024-6832 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 0.25% chance of exploitation in the next 30 days.

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.

Metrics

CVSS 3.1
7.5/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS Probability
0.25%

16.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
Wso2Api Control Plane4.5.0
Wso2Api Control Plane4.6.0
Wso2Api Manager3.1.0
Wso2Api Manager3.2.0
Wso2Api Manager3.2.1
Wso2Api Manager4.1.0
Wso2Api Manager4.2.0
Wso2Api Manager4.3.0
Wso2Api Manager4.4.0
Wso2Api Manager4.5.0
Wso2Api Manager4.6.0
Wso2Identity Server5.10.0
Wso2Identity Server5.11.0
Wso2Identity Server6.0.0
Wso2Identity Server6.1.0
Wso2Identity Server7.0.0
Wso2Identity Server As Key Manager5.10.0
Wso2Open Banking Am2.0.0
Wso2Open Banking Iam2.0.0
Wso2Traffic Manager4.5.0
Wso2Traffic Manager4.6.0
Wso2Universal Gateway4.5.0
Wso2Universal Gateway4.6.0

References

Timeline

Published
Last Modified
Status
Analyzed

Frequently Asked Questions

What is CVE-2024-6832?
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.
How severe is CVE-2024-6832?
CVE-2024-6832 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 0.25% probability of exploitation in the next 30 days.
How do I fix CVE-2024-6832?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2024

Are you affected by CVE-2024-6832?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST