{"answers":{"affected":"It affects 8 products.","exploited":"There is no known exploitation of CVE-2024-6832 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-6832 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-6832 is a medium-severity vulnerability in Wso2 Api Manager, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-6832 and fix it if it is affected.\n\nWhat it is: CVE-2024-6832 is a medium-severity vulnerability in Wso2 Api Manager, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-6832 in the wild and no public exploit code.\n\nAffected product: Wso2 Api Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-6832/ (Markdown: https://insights.sbomify.com/CVE-2024-6832/index.md)","id":"CVE-2024-6832","markdown":"https://insights.sbomify.com/CVE-2024-6832/index.md","name":"CVE-2024-6832","record":{"aliases":["GHSA-fr4m-mcg5-8cpc"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"WSO2 Identity Server","requires_auth":"none","summary":"Attackers can bypass account lockout mechanisms when secondary user stores are inaccessible, enabling brute force attacks against user accounts.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WSO2","cpe":[{"product":"api_control_plane","vendor":"wso2"},{"product":"api_manager","vendor":"wso2"},{"product":"identity_server","vendor":"wso2"},{"product":"identity_server_as_key_manager","vendor":"wso2"},{"product":"open_banking_am","vendor":"wso2"},{"product":"open_banking_iam","vendor":"wso2"},{"product":"traffic_manager","vendor":"wso2"},{"product":"universal_gateway","vendor":"wso2"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"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.\n\nWhen 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Account Lockout Failure via Secondary User Store Inaccessibility in Multiple WSO2 Products Allows Brute Force Attacks","id":"CVE-2024-6832","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wso2:api_manager","products":["wso2:api_manager","wso2:identity_server","wso2:identity_server_as_key_manager"],"type":"security_feature_bypass","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Zowe CLI Auto-Init Leaks Credentials Locally","id":"CVE-2024-6833"},"packages":[],"prev":{"headline":"Missing authorization in AXIS Camera Station","id":"CVE-2024-6831"},"products":["WSO2 API Control Plane","WSO2 API Manager","WSO2 Carbon User Manager Kernel","WSO2 Enterprise Integrator","WSO2 Identity Server","WSO2 Identity Server as Key Manager","WSO2 Open Banking AM","WSO2 Open Banking IAM","WSO2 Traffic Manager","WSO2 Universal Gateway"],"published":"2026-08-06","related":[{"cvss_score":10,"headline":"WSO2 Multiple Products Path Traversal Vulnerability","id":"CVE-2026-5430","kev_date_added":"2026-09-24","published":"2026-08-06"},{"cvss_score":9.8,"headline":"Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover","id":"CVE-2026-1728","kev_date_added":null,"published":"2026-08-06"},{"cvss_score":9.8,"headline":"Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products","id":"CVE-2025-9312","kev_date_added":null,"published":"2025-11-18"},{"cvss_score":9.8,"headline":"Potential Broken Access Control in Multiple WSO2 Products via System REST APIs","id":"CVE-2025-10611","kev_date_added":null,"published":"2025-10-16"},{"cvss_score":9.8,"headline":"Improper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint","id":"CVE-2025-9152","kev_date_added":null,"published":"2025-10-16"},{"cvss_score":9.6,"headline":"Improper Access Control in Multiple WSO2 Products via Internal SOAP Admin Services and System REST APIs","id":"CVE-2025-9804","kev_date_added":null,"published":"2025-10-16"},{"cvss_score":9.4,"headline":"Account Takeover via Conditional Authentication Script Logic in Multiple WSO2 Products","id":"CVE-2025-15039","kev_date_added":null,"published":"2026-08-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-06","vendors":["WSO2"]},"summary":"Attackers can bypass account lockout mechanisms when secondary user stores are inaccessible, enabling brute force attacks against user accounts.","url":"https://insights.sbomify.com/CVE-2024-6832/"}