How severe is GHSA-jqhq-pfg3-fg5p?

GHSA-jqhq-pfg3-fg5p has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jqhq-pfg3-fg5p?

GHSA-jqhq-pfg3-fg5p affects the following packages: Blink1Control2 (npm). Ecosystems affected: npm.

How do I fix GHSA-jqhq-pfg3-fg5p?

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

How do I detect GHSA-jqhq-pfg3-fg5p in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Blink1Control2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-jqhq-pfg3-fg5p 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.

How does O3 Security protect against GHSA-jqhq-pfg3-fg5p?

O3 pinpoints whether GHSA-jqhq-pfg3-fg5p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-jqhq-pfg3-fg5p actively exploited in the wild?

Yes. There are 3 known exploit references for GHSA-jqhq-pfg3-fg5p, 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.

When was GHSA-jqhq-pfg3-fg5p published, and has it been updated?

GHSA-jqhq-pfg3-fg5p was published on September 8, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-jqhq-pfg3-fg5p

HIGHFix: todbot/Blink1Control2@7482746

GHSA-jqhq-pfg3-fg5p is a high-severity (CVSS 7.5) vulnerability in Blink1Control2. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-jqhq-pfg3-fg5p is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Blink1Control2 uses weak password encryption

Also known asCVE-2022-35513

Published

Sep 8, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

Real-World Exposure

1 pkg affected

📦Blink1Control2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update Blink1Control2 to 2.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jqhq-pfg3-fg5p 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.
How O3 protects you
O3 pinpoints whether GHSA-jqhq-pfg3-fg5p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jqhq-pfg3-fg5p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-jqhq-pfg3-fg5p in your dependencies?

O3 detects GHSA-jqhq-pfg3-fg5p across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works