Reversible One-Way Hash Affecting aspnetcore-runtime-6.0 package, versions <0:6.0.26-1.el8_9


Severity

Recommended
high

Based on CentOS security rating.

Threat Intelligence

EPSS
0.13% (48th 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 Reversible One-Way Hash vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CENTOS8-ASPNETCORERUNTIME60-6037892
  • published27 Oct 2023
  • disclosed25 Oct 2023

Introduced: 25 Oct 2023

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

How to fix?

Upgrade Centos:8 aspnetcore-runtime-6.0 to version 0:6.0.26-1.el8_9 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream aspnetcore-runtime-6.0 package and not the aspnetcore-runtime-6.0 package as distributed by Centos. See How to fix? for Centos:8 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 Scores

version 3.1