CVE-2022-35513: The Blink1Control2 application <= 2.2.7 uses weak password encryption and an insecure method of storage.

Q: How do I fix CVE-2022-35513?

blink1control2: upgrade to newer than 2.2.7. Exact commands for each OS are on this page.

Q: Is CVE-2022-35513 being exploited?

CVE-2022-35513 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-35513 affect?

CVE-2022-35513 affects blink1control2. Severity is high (CVSS 7.5). The Blink1Control2 application <= 2.2.7 uses weak password encryption and an insecure method of storage.

Q: How urgent is CVE-2022-35513?

Priority 60/100. High severity; EPSS top 7%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2022-35513 is a high-severity flaw (CVSS 7.5) affecting blink1control2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
EPSS top 7%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	6.0% (top 7%)
CISA exploited list	No
Weakness	CWE-327, CWE-922
Published	2022-09-07
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: blink1

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-09-07 14:15 UTCPublished CVE record published
2026-06-17 04:51 UTCUpdated Record last modified

blink1 blink1control2 UPGRADE

Affected: <= 2.2.7

Fixed in: newer than 2.2.7

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy blink1control2 || rpm -q blink1control2 || blink1control2 --version

2. UPGRADE to newer than 2.2.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade blink1control2

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade blink1control2

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: Blink1Control2 2.2.7 - Weak Password Encryption

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-35513?

blink1control2: upgrade to newer than 2.2.7. Exact commands for each OS are on this page.

Is CVE-2022-35513 being exploited?

CVE-2022-35513 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-35513 affect?

CVE-2022-35513 affects blink1control2. Severity is high (CVSS 7.5). The Blink1Control2 application <= 2.2.7 uses weak password encryption and an insecure method of storage.

How urgent is CVE-2022-35513?

Priority 60/100. High severity; EPSS top 7%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs