Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2024-5617— Account Lock Bypass via User Store Synchronization in Multiple WSO2 Products Allows Brute Force Attacks

Quick assessment

Affected
WSO2 WSO2 API Manager
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

账户锁定功能在主要用户存储和次要用户存储中存在同名用户时，无法对主要用户存储中的账户正确执行锁定策略。该问题产生的原因是：在此类场景下，锁定条件仅应用于次要用户存储中的账户，导致攻击者仍可针对主要用户存储中的账户持续进行身份验证尝试。 此功能缺陷使得暴力破解攻击成为可能。攻击者可通过系统性地针对主要用户存储账户尝试不同密码，从而可能获取敏感信息或账户的非授权访问权限，因为预期的账户锁定机制未能阻止重复的登录尝试。

CVSS 4.8 · Medium

Possible ATT&CK Techniques 1 AI

T1110.001 · Password Guessing
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2024-5617

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Account Lock Bypass via User Store Synchronization in Multiple WSO2 Products Allows Brute Force Attacks
Source: CVE Program / CVE List V5
Vulnerability Description
The account lock feature fails to correctly enforce account lockouts on the primary user store when users with identical usernames exist in both primary and secondary user stores. This occurs because the lock condition is only applied to the secondary user store account in such scenarios, allowing continued authentication attempts against the primary user store account. This functional flaw enables brute force attacks. By systematically attempting different passwords against the primary user store account, an attacker can potentially gain unauthorized access to sensitive information or accounts, as the intended account lockout mechanism does not prevent repeated login attempts.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
交互频率的控制不恰当
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
WSO2 WSO2 API Manager 4.0.0 ~ 4.0.0.298 -
WSO2 WSO2 Identity Server 5.11.0 ~ 5.11.0.348 -
WSO2 WSO2 Carbon Identity Management 5.18.187 ~ 5.18.187.259 -
WSO2 WSO2 Carbon User Manager Kernel 4.6.1 ~ 4.6.1.114 -

II. Public POCs for CVE-2024-5617

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-5617

请登录查看更多情报信息。

Other References for CVE-2024-5617 (1)

Same Patch Batch · WSO2 · 2026-11-02 · 10 CVEs total

CVE-2025-11969 9.4 CRITICAL Broken Access Control via System REST APIs in Multiple WSO2 Products Allows Unauthorized A
CVE-2026-2613 8.7 HIGH SQL Injection via Admin REST API in Multiple WSO2 Products Allows Database Information Inf
CVE-2025-13647 5.8 MEDIUM Information Disclosure in Multiple WSO2 Products Allows Exposure of Certificate File Paths
CVE-2024-2372 5.4 MEDIUM Open Redirection via Unsanitized User Input in Multiple WSO2 Products Allows Phishing Atta
CVE-2024-9517 4.9 MEDIUM Improper Token Renewal in Refresh Token Grant in Multiple WSO2 Products Allows Unauthorize
CVE-2025-12544 4.8 MEDIUM Stored Cross-Site Scripting in Multiple WSO2 Products
CVE-2024-7075 4.6 MEDIUM Reflected Cross-Site Scripting via User Search Function in Management Console of Multiple
CVE-2026-18800 4.4 MEDIUM Information Disclosure via Event Publisher Logging in Multiple WSO2 Products Allows Retrie
CVE-2024-12141 4.3 MEDIUM Open Redirect via Callback URL Validation in WSO2 Products Allows Phishing Attacks

IV. Related Vulnerabilities

Same product: WSO2 API Manager
Same vendor: WSO2
Same weakness: CWE-799