Blink1Control2 up to 2.2.7 weak password

Summaryinfo

A vulnerability identified as critical has been detected in Blink1Control2 up to 2.2.7. The affected element is an unknown function. The manipulation leads to weak password. This vulnerability is traded as CVE-2022-35513. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability was found in Blink1Control2 up to 2.2.7 and classified as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a weak password vulnerability. Using CWE to declare the problem leads to CWE-521. The product does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts. Impacted is confidentiality. The summary by CVE is:

The Blink1Control2 application <= 2.2.7 uses weak password encryption and an insecure method of storage.

The weakness was shared 09/07/2022. The advisory is shared at github.com. The identification of this vulnerability is CVE-2022-35513 since 07/11/2022. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1552 for this issue.

The exploit is available at exploit-db.com. It is declared as proof-of-concept.

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

The vulnerability is also documented in the vulnerability database at Exploit-DB (51014). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• Blink1Control2

Version

• 2.2.0
• 2.2.1
• 2.2.2
• 2.2.3
• 2.2.4
• 2.2.5
• 2.2.6
• 2.2.7

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion