CVE-2022-35513
HIGHCVSS 7.5/10EPSS 4.14%
Last modified
CVE-2022-35513 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. The Blink1Control2 application <= 2.2.7 uses weak password encryption and an insecure method of storage.. EPSS estimates a 4.14% chance of exploitation in the next 30 days.
Description
The Blink1Control2 application <= 2.2.7 uses weak password encryption and an insecure method of storage.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Blink1 | Blink1control2 | <= 2.2.7 |
References
- http://packetstormsecurity.com/files/168428/Blink1Control2-2.2.7-Weak-Password-Encryption.htmlExploit, Third Party Advisory, VDB Entry
- https://github.com/p1ckzi/CVE-2022-35513Exploit, Third Party Advisory
- https://github.com/todbot/Blink1Control2/releasesRelease Notes, Third Party Advisory
- http://packetstormsecurity.com/files/168428/Blink1Control2-2.2.7-Weak-Password-Encryption.htmlExploit, Third Party Advisory, VDB Entry
- https://github.com/p1ckzi/CVE-2022-35513Exploit, Third Party Advisory
- https://github.com/todbot/Blink1Control2/releasesRelease Notes, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-35513?
The Blink1Control2 application <= 2.2.7 uses weak password encryption and an insecure method of storage.
How severe is CVE-2022-35513?
CVE-2022-35513 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 4.14% probability of exploitation in the next 30 days.
How do I fix CVE-2022-35513?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2022-35513?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST