CVE-2022-35513 — The Blink1Control2 application <= 2
The Blink1Control2 application <= 2.2.7 uses weak password encryption and an insecure method of storage.
Published
2022-09-07T13:54:18.000Z
Last modified
2024-08-03T09:36:44.243Z
01What is this vulnerability?
The Blink1Control2 application <= 2.2.7 uses weak password encryption and an insecure method of storage.
02Affected products
| Vendor | Product | Versions |
|---|
| n | a / n/a | n/a |
03Active exploitation status
Not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog. EPSS is the best forward-looking signal — see the EPSS row above.
04Recommended remediation
- Patch to a fixed version listed in the vendor advisory (see references below).
- Mitigate with WAF rules, network egress filters, or feature flags where the patch is not yet available.
- Hunt historical logs for exploitation indicators — see Detection signatures below.
05Technical details
For the full vendor write-up, exploit chains, and reference implementations, see the references list in section 09.
06Detection signatures
Ask SARA in chat to draft a starting detection for this CVE in your stack of choice.
07Related CVEs
No directly-cited follow-up CVEs in the KB record for this advisory. The references list in section 09 carries the vendor cross-references.
08Timeline
- Published: 2022-09-07T13:54:18.000Z
- Last modified: 2024-08-03T09:36:44.243Z
09References
- github.com — https://github.com/todbot/Blink1Control2/releases
- github.com — https://github.com/p1ckzi/CVE-2022-35513
- packetstormsecurity.com — http://packetstormsecurity.com/files/168428/Blink1Control2-2.2.7-Weak-Password-E…
Want this in your SOAR or SIEM?
SARA's API returns EPSS, CVSS, KEV, and an analyst-grade summary in one call.
Read the API reference →