How severe is CVE-2022-35513?

CVE-2022-35513 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-35513?

CVE-2022-35513 affects the following packages: Blink1Control2 (npm). Ecosystems affected: npm.

How do I fix CVE-2022-35513?

Update Blink1Control2 to 2.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-35513 is resolved across your whole dependency graph.

How do I detect CVE-2022-35513 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Blink1Control2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-35513 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-35513 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2022-35513, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-35513?

CVE-2022-35513 has an EPSS (Exploit Prediction Scoring System) score of 6.2%, placing it in the 93th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-35513?

CVE-2022-35513 is classified as Broken Cryptographic Algorithm (CWE-327), CWE-922 (CWE-922). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-35513 published, and has it been updated?

CVE-2022-35513 was published on September 7, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

CVE-2022-35513 — Blink1Control2

HIGHFix: todbot/Blink1Control2@7482746

CVE-2022-35513 is a high-severity (CVSS 7.5) Broken Cryptographic Algorithm vulnerability in Blink1Control2. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for Blink1Control2 — see the affected versions and patch details below.

Blink1Control2 uses weak password encryption

Also known asGHSA-jqhq-pfg3-fg5p

Published

Sep 7, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

6.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

Blink1Control2npm

32downloads / week

Description

The Blink1Control2 application <= 2.2.7 uses weak password encryption and an insecure method of storage. Version 2.2.9 fixes the issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`Blink1Control2`	all versions	2.2.9`npm install Blink1Control2@2.2.9`

Affected Products

1 product · 1 configurations

Application

blink1control2blink1

≤ 2.2.7

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-51014localmultiple

Blink1Control2 2.2.7 - Weak Password Encryption

by p1ckzi · Sep 20, 2022

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Blink1Control2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Blink1Control2 to 2.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-35513 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

The Blink1Control2 application <= 2.2.7 uses weak password encryption and an insecure method of storage. Version 2.2.9 fixes the issue.

O3 Security · Impact-Aware SCA

Is CVE-2022-35513 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works