Use of a Broken or Risky Cryptographic Algorithm Affecting cryptojs package, versions *


Severity

Recommended
medium

Based on Ubuntu security rating.

Threat Intelligence

EPSS
0.13% (49th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Use of a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-UBUNTU2310-CRYPTOJS-6036951
  • published26 Apr 2024
  • disclosed25 Oct 2023

Introduced: 25 Oct 2023

CVE-2023-46233  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

There is no fixed version for Ubuntu:23.10 cryptojs.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cryptojs package and not the cryptojs package as distributed by Ubuntu. See How to fix? for Ubuntu:23.10 relevant fixed versions and status.

crypto-js is a JavaScript library of crypto standards. Prior to version 4.2.0, crypto-js PBKDF2 is 1,000 times weaker than originally specified in 1993, and at least 1,300,000 times weaker than current industry standard. This is because it both defaults to SHA1, a cryptographic hash algorithm considered insecure since at least 2005, and defaults to one single iteration, a 'strength' or 'difficulty' value specified at 1,000 when specified in 1993. PBKDF2 relies on iteration count as a countermeasure to preimage and collision attacks. If used to protect passwords, the impact is high. If used to generate signatures, the impact is high. Version 4.2.0 contains a patch for this issue. As a workaround, configure crypto-js to use SHA256 with at least 250,000 iterations.

CVSS Base Scores

version 3.1