Brokerage Technology Solutions Wave 2.0 up to 1.1.6 API Based Login excessive authentication

Summaryinfo

A vulnerability classified as problematic has been found in Brokerage Technology Solutions Wave 2.0 up to 1.1.6. The affected element is an unknown function of the component API Based Login. Performing a manipulation results in excessive authentication. This vulnerability is identified as CVE-2024-51558. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Brokerage Technology Solutions Wave 2.0 up to 1.1.6. This affects some unknown processing of the component API Based Login. The manipulation with an unknown input leads to a excessive authentication vulnerability. CWE is classifying the issue as CWE-307. The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks. This is going to have an impact on confidentiality. The summary by CVE is:

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.

The weakness was released by Mohit Gadiya as CIVN-2024-0332. The advisory is shared at cert-in.org.in. This vulnerability is uniquely identified as CVE-2024-51558 since 10/29/2024. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1110.001 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Brokerage Technology Solutions

Name

• Wave 2.0

Version

• 1.1.0
• 1.1.1
• 1.1.2
• 1.1.3
• 1.1.4
• 1.1.5
• 1.1.6

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion