MB connect line mymbCONNECT24/mbCONNECT24 up to 2.6.2 Login excessive authentication

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.7$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in MB connect line mymbCONNECT24 and mbCONNECT24 up to 2.6.2. The affected element is an unknown function of the component Login Handler. Performing a manipulation results in excessive authentication. This vulnerability is cataloged as CVE-2020-35565. It is possible to initiate the attack remotely. There is no exploit available. The suggested workaround should be applied.

Detailsinfo

A vulnerability was found in MB connect line mymbCONNECT24 and mbCONNECT24 up to 2.6.2. It has been classified as problematic. This affects an unknown functionality of the component Login Handler. 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 weakness was shared 02/16/2021 as vde-2021-003. The advisory is shared at cert.vde.com. This vulnerability is uniquely identified as CVE-2020-35565. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1110.001 for this issue.

The best possible mitigation is suggested to be Workaround.

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

Productinfo

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.7
VulDB Meta Temp Score: 6.7

VulDB Base Score: 3.7
VulDB Temp Score: 3.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Excessive authentication
CWE: CWE-307 / CWE-799 / CWE-400
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Workaround
Status: 🔍

0-Day Time: 🔍

Workaround: Enable bruteforce detection

Timelineinfo

12/18/2020 🔍
02/16/2021 +60 days 🔍
02/16/2021 +0 days 🔍
03/02/2021 +14 days 🔍

Sourcesinfo

Advisory: vde-2021-003
Status: Not defined

CVE: CVE-2020-35565 (🔍)
GCVE (CVE): GCVE-0-2020-35565
GCVE (VulDB): GCVE-100-169989

Entryinfo

Created: 02/16/2021 22:12
Updated: 03/02/2021 07:54
Changes: 02/16/2021 22:12 (37), 03/01/2021 11:36 (2), 03/02/2021 06:47 (2), 03/02/2021 06:49 (18), 03/02/2021 07:53 (1), 03/02/2021 07:54 (3)
Complete: 🔍
Committer: Anonymous User
Cache ID: 216::103

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!