CVE-2022-35513

Public Exploit

Description

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

Category

7.5
CVSS
Severity: High
CVSS 3.1 •
EPSS 5.80% Top 10%
Third-Party Advisory packetstormsecurity.com Third-Party Advisory github.com Third-Party Advisory github.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://github.com/todbot/Blink1Control2/releases third party advisory release notes
https://github.com/p1ckzi/CVE-2022-35513 third party advisory exploit
http://packetstormsecurity.com/files/168428/Blink1Control2-2.2.7-Weak-Password-Encryption.html exploit vdb entry third party advisory

Frequently Asked Questions

What is the severity of CVE-2022-35513?
CVE-2022-35513 has been scored as a high severity vulnerability.
How to fix CVE-2022-35513?
To fix CVE-2022-35513, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-35513 being actively exploited in the wild?
It is possible that CVE-2022-35513 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~6% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.