CVE-2022-35513

Exp

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

Published: 2022-09-07 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-35513 is rated High Exploit Risk (76.8/100): CVSS High severity, with high exploitation likelihood (EPSS 4.39%, 90th percentile). 3 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-35513

EDB-ID Source Kind Published Link
51014 exploit_db edb 2022-09-20 Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-35513

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-07-08 4.14% 4.39% +0.25%
2 2026-06-18 4.03% 4.14% +0.11%
3 2026-06-15 — 4.03% —

Full EPSS history (31 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-35513

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2022-35513

GitHub Security Advisory for CVE-2022-35513

GHSA-jqhq-pfg3-fg5p · Severity: high · Ecosystem: npm — Blink1Control2 uses weak password encryption

Affected software / configurations for CVE-2022-35513

Vendor Product Version Raw CPE
blink1 blink1control2 <= 2.2.7 cpe:2.3:a:blink1:blink1control2:*:*:*:*:*:*:*:*

References for CVE-2022-35513

cvelogic Threat Intelligence