Skip to content

Blink1Control2 uses weak password encryption

High severity GitHub Reviewed Published Sep 8, 2022 to the GitHub Advisory Database • Updated Jan 30, 2023

Package

npm Blink1Control2 (npm)

Affected versions

< 2.2.9

Patched versions

2.2.9
Published by the National Vulnerability Database Sep 7, 2022
Published to the GitHub Advisory Database Sep 8, 2022
Reviewed Sep 16, 2022
Last updated Jan 30, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

20.958%
(97th percentile)

Weaknesses

CVE ID

CVE-2022-35513

GHSA ID

GHSA-jqhq-pfg3-fg5p

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.