# Blink1Control2 uses weak password encryption

Advisory record · `GHSA-jqhq-pfg3-fg5p`

- **Identifiers:** `GHSA-jqhq-pfg3-fg5p` · `CVE-2022-35513`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-326](https://cwe.mitre.org/data/definitions/326.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 8 Sept 2022
- **Updated:** 8 Nov 2023
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 Sept 2022, 00:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `Blink1Control2` (npm): affected `<2.2.9`; fixed in `2.2.9`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.062, the 93rd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 8 Sept 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-jqhq-pfg3-fg5p](https://github.com/advisories/GHSA-jqhq-pfg3-fg5p)
- [OSV: GHSA-jqhq-pfg3-fg5p](https://osv.dev/vulnerability/GHSA-jqhq-pfg3-fg5p)
- <https://nvd.nist.gov/vuln/detail/CVE-2022-35513>
- <https://github.com/todbot/Blink1Control2/issues/175>
- <https://github.com/todbot/Blink1Control2/commit/74827462aba3a26d7bf157522f69eec999d7ba85>
- <https://github.com/todbot/Blink1Control2/commit/cd9229ef9131bc663f714150c9f8d5cbf818d620>
- <https://github.com/todbot/Blink1Control2/commit/efe174823f67bbdcee8863e02df67a130f132075>
- <https://github.com/todbot/Blink1Control2/commit/f595d782d2356878188fed423a7dcb84ee8fee9d>
- <https://github.com/p1ckzi/CVE-2022-35513>
- <https://github.com/todbot/Blink1Control2>
- <https://github.com/todbot/Blink1Control2/releases>
- <http://packetstormsecurity.com/files/168428/Blink1Control2-2.2.7-Weak-Password-Encryption.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jqhq-pfg3-fg5p>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jqhq-pfg3-fg5p/>. Everything for agents: <https://agentprime.io/llms.txt>.
