# Leakage of sensitive data in local storage

## Overview

* **Rule ID**: `javascript_lang_session`
* **Applicable Languages**: Javascript
* **Weakness ID**: CWE-312

## Description

Storing sensitive data in localStorage presents a security risk. This vulnerability arises when sensitive information is kept in the browser's local storage, leaving it exposed to unauthorized access.

## Remediation Guidelines

* **Avoid** storing sensitive data in `localStorage`. This practice exposes sensitive information to potential security vulnerabilities.

  ```javascript
  localStorage.setItem('user', email); // insecure
  ```
* **Use** server-based session storage solutions to keep session data secure. This method reduces the risk of sensitive data exposure.
* **Store only non-sensitive data in `localStorage`**, such as a unique identifier, to mitigate security risks.

  ```javascript
  localStorage.setItem('user', user.uuid);
  ```

## References

* [**OWASP sensitive data exposure**](https://owasp.org/www-project-top-ten/2017/A3_2017-Sensitive_Data_Exposure)
* [**CWE-312: Cleartext Storage of Sensitive Information**](https://cwe.mitre.org/data/definitions/312.html)
* [**OWASP Top 10: A04:2021 - Insecure Design**](https://owasp.org/Top10/A04_2021-Insecure_Design/)

## 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)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sec1.io/user-docs/4-sast/3-javascript/leakage-of-sensitive-data-in-local-storage.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.