How severe is CVE-2022-35513?

CVE-2022-35513 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2022-35513 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (90th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-35513?

CVE-2022-35513 affects Blink1 Blink1control2. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2022-35513?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2022-35513 published?

CVE-2022-35513 was published on 2022-09-07 and last updated on 2026-06-17.

CVE-2022-35513

CVE-2022-35513 is a high-severity vulnerability in Blink1 Blink1control2 with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-327.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 4% (90th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-327
Affected product: Blink1 Blink1control2
Published: 2022-09-07
Last modified: 2026-06-17

Description

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

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 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2022-35513 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (90th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-35513?: CVE-2022-35513 affects Blink1 Blink1control2. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-35513?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-35513 published?: CVE-2022-35513 was published on 2022-09-07 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:blink1:blink1control2:*:*:*:*:*:*:*:*

Other CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities

CVE-2026-50086 — Critical (CVSS 10.0): The Aqara IAM/SSO gateway (gw-builder.aqara.com) exposes bidirectional AES round-trups against the platform's signing…
CVE-2026-21718 — Critical (CVSS 10.0): An authentication bypass vulnerability exists in Copeland XWEB Pro version 1.12.1 and prior, enabling any attackers to…
CVE-2025-54426 — Critical (CVSS 9.9): Polkadot Frontier is an Ethereum and EVM compatibility layer for Polkadot and Substrate. In versions prior to commit…
CVE-2024-51478 — Critical (CVSS 9.9): YesWiki is a wiki system written in PHP. Prior to 4.4.5, the use of a weak cryptographic algorithm and a hard-coded…
CVE-2026-28252 — Critical (CVSS 9.8): A Use of a Broken or Risky Cryptographic Algorithm vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge…
CVE-2025-13476 — Critical (CVSS 9.8): Rakuten Viber Cloak mode in Android v25.7.2.0g and Windows v25.6.0.0–v25.8.1.0 uses a static and predictable TLS…

Browse all CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities →