Advisory Database
  • Advisories
  • Dependency Scanning
  1. npm
  2. ›
  3. @devicefarmer/stf
  4. ›
  5. CVE-2023-51839

CVE-2023-51839: Use of a Broken or Risky Cryptographic Algorithm

January 29, 2024 (updated February 6, 2024)

DeviceFarmer stf v3.6.6 suffers from Use of a Broken or Risky Cryptographic Algorithm.

References

  • github.com/DeviceFarmer/stf
  • github.com/DeviceFarmer/stf/blob/a6b5f18941d0de5929f9c24c3ce3e9c13317a653/lib/util/vncauth.js
  • github.com/DeviceFarmer/stf/issues/736
  • github.com/advisories/GHSA-7xm8-wjq7-88r5
  • github.com/tianjk99/Cryptographic-Misuses/blob/main/CVE-2023-51839.md
  • nvd.nist.gov/vuln/detail/CVE-2023-51839

Code Behaviors & Features

Detect and mitigate CVE-2023-51839 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions up to 3.6.6

Solution

Unfortunately, there is no solution available yet.

Impact 9.1 CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Learn more about CVSS

Weakness

  • CWE-327: Use of a Broken or Risky Cryptographic Algorithm

Source file

npm/@devicefarmer/stf/CVE-2023-51839.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 14 May 2025 12:14:48 +0000.