> 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/unsanitized-user-input-in-deserialization-method-lang.md).

# Unsanitized user input in deserialization method

## Overview

* **Rule ID**: `javascript_lang_unsafe_deserialization`
* **Applicable Languages**: Javascript
* **Weakness ID**: CWE-502

## Description

Deserializing untrusted data is a dangerous practice. This vulnerability occurs when data, especially from external sources such as request objects, is deserialized without proper sanitization. Attackers can insert malicious payloads within serialized data, compromising your application's security upon deserialization.

## Remediation Guidelines

* **Avoid** deserializing data that originates from untrusted sources. This helps prevent attackers from injecting malicious payloads that could jeopardize your application.
* **Choose** data-only and language-neutral serialization formats such as JSON or XML for deserializing data. These formats are less prone to manipulation by attackers attempting to exploit the deserialization process.

  ```javascript
  JSON.parse(req.params);
  ```

## References

* [**OWASP Deserialization cheat sheet**](https://cheatsheetseries.owasp.org/cheatsheets/Deserialization_Cheat_Sheet.html)
* [**CWE-502: Deserialization of Untrusted Data**](https://cwe.mitre.org/data/definitions/502.html)
* [**OWASP Top 10: A08:2021 - Software and Data Integrity Failures**](https://owasp.org/Top10/A08_2021-Software_and_Data_Integrity_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)