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

# Leakage of Information in Logger Message

## Overview

* **Rule ID**: `java_lang_logger_leak`
* **Applicable Languages**: Java
* **Weakness ID**: CWE-532

## Description

Information leakage through logger messages can compromise sensitive data. This vulnerability arises when dynamic data or variables, which may contain sensitive information, are included in log messages.

## Remediation Guidelines

* **Do not** include variables or dynamic data containing sensitive information in logger messages. This can inadvertently expose sensitive data in logs, which are often not adequately protected.

  ```java
  logger.info("user signed in: " + user.uuid) // unsafe

  ```
* Instead, **Do log** static messages that do not contain dynamic variables or attributes. This minimizes the risk of accidentally logging sensitive information.

  ```java
  logger.info("user signed in")
  ```

## References

* [**OWASP Logging Cheat Sheet**](https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html)
* [**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)