Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By WSO2

  2. · 2 years later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-5617, by who scored it
Scored byCVSSScoreVector
WSO2CNA (assigner)3.1Medium4.8CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
NVDNVD · Awaiting Analysis3.1Medium4.8CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.8.

Affected products

  • WSO2 · WSO2 API Manager

    • unknown < 4.0.0
    • affected 4.0.0 – < 4.0.0.298
    • affected 4.2.0 – < 4.2.0.95
    • affected 4.3.0 – < 4.3.0.13
  • WSO2 · WSO2 Identity Server

    • unknown < 5.11.0
    • affected 5.11.0 – < 5.11.0.348
    • affected 6.0.0 – < 6.0.0.194
    • affected 6.1.0 – < 6.1.0.162
    • affected 7.0.0 – < 7.0.0.33
  • WSO2 · WSO2 Carbon Identity Management

    • affected 5.18.187 – < 5.18.187.259
    • affected 5.23.8 – < 5.23.8.180
    • affected 5.24.8 – < 5.24.8.5
    • affected 5.25.92 – < 5.25.92.84
    • affected 5.25.705 – < 5.25.705.5
    • affected 7.0.78 – < 7.0.78.19
  • WSO2 · WSO2 Carbon User Manager Kernel

    • affected 4.6.1 – < 4.6.1.114
    • affected 4.7.1 – < 4.7.1.53
    • affected 4.8.1 – < 4.8.1.16
    • affected 4.9.0 – < 4.9.0.58
    • affected 4.9.26 – < 4.9.26.7
    • affected 4.10.9 – < 4.10.9.17

What to do

Solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3414/#solution https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3414/#solution

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-5617 badge
[![CVE-2024-5617](https://cveledger.app/badge/CVE-2024-5617.svg)](https://cveledger.app/cve/CVE-2024-5617)

Record last updated .