Skip to content

Ylianst MeshCentral 1.1.16 suffers from Use of a Broken or Risky Cryptographic Algorithm.

High severity GitHub Reviewed Published Feb 2, 2024 to the GitHub Advisory Database • Updated Feb 12, 2024

Package

npm meshcentral (npm)

Affected versions

<= 1.1.16

Patched versions

None
Published by the National Vulnerability Database Feb 2, 2024
Published to the GitHub Advisory Database Feb 2, 2024
Reviewed Feb 2, 2024
Last updated Feb 12, 2024

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

0.071%
(33rd percentile)

Weaknesses

CVE ID

CVE-2023-51838

GHSA ID

GHSA-v269-rrr6-cx6r

Source code

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