Vulnerability record · CVE-2022-35513 · published 7 September 2022
CVE-2022-35513: Blink1control2 broken cryptographic algorithm vulnerability
Blink1 · Blink1control2
The Blink1Control2 application <= 2.2.7 uses weak password encryption and an insecure method of storage.
Description
The Blink1Control2 application <= 2.2.7 uses weak password encryption and an insecure method of storage.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| http://packetstormsecurity.com/files/168428/Blink1Control2-2.2.7-Weak-Password-Encryption.html | ExploitThird Party AdvisoryVDB Entry |
| https://github.com/p1ckzi/CVE-2022-35513 | ExploitThird Party Advisory |
| https://github.com/todbot/Blink1Control2/releases | Release NotesThird Party Advisory |
| http://packetstormsecurity.com/files/168428/Blink1Control2-2.2.7-Weak-Password-Encryption.html | ExploitThird Party AdvisoryVDB Entry |
| https://github.com/p1ckzi/CVE-2022-35513 | ExploitThird Party Advisory |
| https://github.com/todbot/Blink1Control2/releases | Release NotesThird Party Advisory |
Track CVE-2022-35513 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Source: NIST National Vulnerability Database (record CVE-2022-35513), CISA KEV, FIRST EPSS (scores of 2026-09-27). This page is refreshed as NVD updates the record.