> For the complete documentation index, see [llms.txt](https://docs.sec1.io/user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sec1.io/user-docs/4-sast/3-javascript/usage-of-weak-hashing-library-sha1.md).

# Usage of weak hashing library (SHA-1)

## Overview

* **Rule ID**: `javascript_lang_weak_hash_sha1`
* **Applicable Languages**: Javascript
* **Weakness ID**: CWE-328

## Description

Using a weak hashing library such as SHA-1 heightens the risk of data breaches. SHA-1 is especially prone to collision attacks, where distinct inputs can generate the same hash value, thereby compromising data integrity and security.

## Remediation Guidelines

* **Do not** use SHA-1 for hashing. It's no longer considered secure against well-funded attackers.

  ```javascript
  const hash = crypto.createHmac("sha1", key).update(user.password); // unsafe

  ```
* **Do use** stronger hashing algorithms like SHA-256 or SHA-3 for enhanced security.

  ```javascript
  const hash = crypto.createHmac("sha256", key).update(user.password);

  ```

## References

* [**NodeJS Crypto Module**](https://nodejs.org/api/crypto.html)
* [**CWE-328: Use of Weak Hash**](https://cwe.mitre.org/data/definitions/328.html)
* [**OWASP Top 10: A02:2021 - Cryptographic Failures**](https://owasp.org/Top10/A02_2021-Cryptographic_Failures/)

## Configuration

To omit this rule during a scan, and to provide you with continuous 24/7 code-level scanning, you can employ our [**SAST TOOL**](https://scopy.sec1.io/login)