{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2024-51558 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-51558 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-51558 is a critical authentication bypass vulnerability in Brokerage Technology Solutions Wave 2.0, published on 4 Nov 2024. 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-51558 and fix it if it is affected.\n\nWhat it is: CVE-2024-51558 is a critical authentication bypass vulnerability in Brokerage Technology Solutions Wave 2.0, published on 4 Nov 2024. 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-51558 in the wild and no public exploit code.\n\nAffected product: Brokerage Technology Solutions Wave 2.0. 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-51558/ (Markdown: https://insights.sbomify.com/CVE-2024-51558/index.md)","id":"CVE-2024-51558","markdown":"https://insights.sbomify.com/CVE-2024-51558/index.md","name":"CVE-2024-51558","record":{"aliases":["GHSA-9xwg-wxgq-6vph"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Wave 2.0 API","requires_auth":"none","summary":"Remote attackers can brute force login credentials due to missing rate limiting, leading to unauthorized account access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-In","cpe":[{"product":"aero","vendor":"63moons"},{"product":"wave_2.0","vendor":"63moons"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"This vulnerability exists in the Wave 2.0 due to missing restrictions for excessive failed authentication attempts on its API based login. A remote attacker could exploit this vulnerability by conducting a brute force attack against legitimate user OTP, MPIN or password, which could lead to gain unauthorized access and compromise other user accounts.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Brute Force Attack Vulnerability in Wave 2.0","id":"CVE-2024-51558","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Access Control Vulnerability in Wave 2.0","id":"CVE-2024-51559"},"packages":[],"prev":{"headline":"No Rate Limiting Vulnerability in Wave 2.0","id":"CVE-2024-51557"},"products":["Wave 2.0"],"published":"2024-11-04","related":[{"cvss_score":9.3,"headline":"Authentication bypass Vulnerability in Aero","id":"CVE-2024-51561","kev_date_added":null,"published":"2024-11-04"},{"cvss_score":7.1,"headline":"Sensitive Information Disclosure Vulnerability in Wave 2.0","id":"CVE-2024-51556","kev_date_added":null,"published":"2024-11-04"},{"cvss_score":7.1,"headline":"No Rate Limiting Vulnerability in Wave 2.0","id":"CVE-2024-51557","kev_date_added":null,"published":"2024-11-04"},{"cvss_score":7.1,"headline":"Improper Access Control Vulnerability in Wave 2.0","id":"CVE-2024-51559","kev_date_added":null,"published":"2024-11-04"},{"cvss_score":7.1,"headline":"Improper Error Handling Vulnerability in Wave 2.0","id":"CVE-2024-51560","kev_date_added":null,"published":"2024-11-04"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-11-04","vendors":["Brokerage Technology Solutions"]},"summary":"Remote attackers can brute force login credentials due to missing rate limiting, leading to unauthorized account access.","url":"https://insights.sbomify.com/CVE-2024-51558/"}