CVE-2024-6832— WSO2多款产品账号锁定失败致暴力破解漏洞
可能的 ATT&CK 技术 1AI
T1110.001 · Password Guessing影响版本矩阵 53
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| WSO2 | WSO2 API Control Plane | < 4.5.0 | unknown |
4.5.0< 4.5.0.40 | affected | ||
4.6.0< 4.6.0.4 | affected | ||
4.6.0< 4.6.0.5 | affected | ||
| WSO2 | WSO2 API Manager | < 3.1.0 | unknown |
3.1.0< 3.1.0.296 | affected | ||
3.2.0< 3.2.0.386 | affected | ||
3.2.0< 3.2.0.455 | affected | ||
3.2.1< 3.2.1.74 | affected | ||
4.1.0< 4.1.0.238 | affected | ||
4.2.0< 4.2.0.179 | affected | ||
4.3.0< 4.3.0.91 | affected | ||
| … +3 条更多 | |||
| WSO2 | WSO2 Carbon User Manager Kernel | 4.5.0< 4.5.0.7 | affected |
4.5.3< 4.5.3.53 | affected | ||
4.6.0< 4.6.0.196 | affected | ||
4.6.1< 4.6.1.163 | affected | ||
4.6.1< 4.6.1.164 | affected | ||
4.6.3< 4.6.3.44 | affected | ||
4.6.4< 4.6.4.25 | affected | ||
4.7.1< 4.7.1.77 | affected | ||
| … +8 条更多 | |||
| WSO2 | WSO2 Enterprise Integrator | < 6.6.0 | unknown |
6.6.0< 6.6.0.229 | affected | ||
| WSO2 | WSO2 Identity Server | < 5.10.0 | unknown |
5.10.0< 5.10.0.320 | affected | ||
5.11.0< 5.11.0.427 | affected | ||
6.0.0< 6.0.0.254 | affected | ||
6.1.0< 6.1.0.195 | affected | ||
7.0.0< 7.0.0.82 | affected | ||
| WSO2 | WSO2 Identity Server as Key Manager | < 5.10.0 | unknown |
5.10.0< 5.10.0.314 | affected | ||
| WSO2 | WSO2 Open Banking AM | < 2.0.0 | unknown |
2.0.0< 2.0.0.345 | affected | ||
| WSO2 | WSO2 Open Banking IAM | < 2.0.0 | unknown |
2.0.0< 2.0.0.366 | affected | ||
| WSO2 | WSO2 Traffic Manager | < 4.5.0 | unknown |
4.5.0< 4.5.0.38 | affected | ||
4.6.0< 4.6.0.4 | affected | ||
4.6.0< 4.6.0.5 | affected | ||
| WSO2 | WSO2 Universal Gateway | < 4.5.0 | unknown |
4.5.0< 4.5.0.38 | affected | ||
4.6.0< 4.6.0.4 | affected | ||
4.6.0< 4.6.0.5 | affected | ||
获取后续新漏洞提醒登录后订阅
一、 漏洞 CVE-2024-6832 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗ 尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
Account Lockout Failure via Secondary User Store Inaccessibility in Multiple WSO2 Products Allows Brute Force Attacks
来源: CVE Program / CVE List V5
Vulnerability 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.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
来源: CVE Program / CVE List V5
Vulnerability Type
保护机制失效
来源: CVE Program / CVE List V5
受影响产品
| 厂商 | 产品 | 影响版本 | CPE | 订阅 |
|---|---|---|---|---|
| WSO2 | WSO2 Enterprise Integrator | 6.6.0 ~ 6.6.0.229 | - | |
| WSO2 | WSO2 API Control Plane | 4.5.0 ~ 4.5.0.40 | - | |
| WSO2 | WSO2 Traffic Manager | 4.5.0 ~ 4.5.0.38 | - | |
| WSO2 | WSO2 Universal Gateway | 4.5.0 ~ 4.5.0.38 | - | |
| WSO2 | WSO2 API Manager | 3.1.0 ~ 3.1.0.296 | - | |
| WSO2 | WSO2 Identity Server | 5.10.0 ~ 5.10.0.320 | - | |
| WSO2 | WSO2 Identity Server as Key Manager | 5.10.0 ~ 5.10.0.314 | - | |
| WSO2 | WSO2 Open Banking IAM | 2.0.0 ~ 2.0.0.366 | - | |
| WSO2 | WSO2 Open Banking AM | 2.0.0 ~ 2.0.0.345 | - | |
| WSO2 | WSO2 Carbon User Manager Kernel | 4.5.0 ~ 4.5.0.7 | - |
二、漏洞 CVE-2024-6832 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2024-6832 的情报信息
请登录查看更多情报信息。
CVE-2024-6832 厂商安全公告 (1)
- 🔗 Security Advisory WSO2-2024-3352/CVE-2024-6832vendor-advisory
同批安全公告 · WSO2 · 2026-08-06 · 共 19 条
| CVE-2026-5430 | 10.0 CRITICAL | 多个WSO2产品JWT算法不匹配导致认证绕过漏洞 |
| CVE-2026-1728 | 9.8 CRITICAL | WSO2多产品REST API权限提升漏洞 |
| CVE-2025-15039 | 9.4 CRITICAL | 多个WSO2产品条件认证脚本逻辑导致账户接管漏洞 |
| CVE-2026-3418 | 9.1 CRITICAL | WSO2产品任意文件上传导致远程代码执行漏洞 |
| CVE-2025-14561 | 9.0 CRITICAL | 多个WSO2产品发布商REST API访问控制绕过 |
| CVE-2026-3415 | 8.7 HIGH | WSO2多个产品XML外部实体注入漏洞 |
| CVE-2024-6541 | 6.8 MEDIUM | WSO2 多个产品消息上下文处理不当导致信息泄露和完整性破坏漏洞 |
| CVE-2025-13394 | 5.4 MEDIUM | WSO2多个产品跨站请求伪造漏洞 |
| CVE-2025-12317 | 5.0 MEDIUM | WSO2多款产品SOAP服务令牌撤销不当致权限保留漏洞 |
| CVE-2024-8995 | 4.9 MEDIUM | 多个WSO2产品已删除用户授权代码重用导致未授权访问 |
| CVE-2026-0637 | 4.4 MEDIUM | 多个WSO2产品通过事件发布者日志敏感信息泄露漏洞 |
| CVE-2025-13909 | 4.3 MEDIUM | WSO2 Identity Server 跨租户PII信息泄露漏洞 |
| CVE-2025-11850 | 4.3 MEDIUM | WSO2 Identity Server 身份混淆漏洞 |
| CVE-2025-6508 | 4.3 MEDIUM | WSO2 API Manager Swagger UI 敏感信息泄露漏洞 |
| CVE-2024-10302 | 4.0 MEDIUM | WSO2多产品注册流程输入验证不当致数据泄露漏洞 |
| CVE-2025-14779 | 3.8 LOW | WSO2 Identity Server 密钥类型管理API访问控制漏洞 |
| CVE-2025-13736 | 3.7 LOW | WSO2多产品登录接口用户名枚举漏洞 |
| CVE-2025-12627 | 2.4 LOW | WSO2 Identity Server 用户模拟流程中刷新令牌实现不当导致未授权操作 |
IV. Related Vulnerabilities
V. Comments for CVE-2024-6832
暂无评论