> 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/leakage-of-information-in-logger-message.md).

# Leakage of information in logger message

## Overview

* **Rule ID**: `javascript_lang_logger_leak`
* **Applicable Languages**: Javascript
* **Weakness ID**: CWE-532

## Description

Information leakage through logger messages can expose sensitive data. This vulnerability occurs when dynamic data or variables, potentially containing sensitive information, are included in log messages.

## Remediation Guidelines

* **Avoid** including sensitive data directly in logger messages, as this can result in the exposure of such data in log files that may be accessible to unauthorized individuals. For example, using

  ```javascript
  logger.info(`Results: ${data}`) // unsafe

  ```
* Instead, **use logging levels appropriately to manage the verbosity** of log output and reduce the risk of disclosing sensitive information in production environments.

## References

* [**CWE-532: Insertion of Sensitive Information into Log File**](https://cwe.mitre.org/data/definitions/532.html)
* [**OWASP Top 10: A09:2021 - Security Logging and Monitoring Failures**](https://owasp.org/Top10/A09_2021-Security_Logging_and_Monitoring_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)