# Leakage of sensitive data in exception message

## Overview

* **Rule ID**: `java_lang_exception`
* **Applicable Languages**: Java
* **Weakness ID**: CWE-210

## Description

Leakage of sensitive data in exception messages can lead to data breaches. This vulnerability occurs when sensitive information is included in exceptions, making it accessible to unauthorized users.

## Remediation Guidelines

* **Avoid** including sensitive data in exception messages to prevent inadvertent exposure of private information.

  ```java
  throw new Exception("error for " + user.email);

  ```
* **Use** non-sensitive, unique identifiers in exception messages to avoid revealing personal identifiable information (PII).

  ```java
  throw new Exception("error for " + user.id);
  ```

## References

* [**CWE-210: Self-generated Error Message Containing Sensitive Information**](https://cwe.mitre.org/data/definitions/210.html)

## 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/2-java/leakage-of-sensitive-data-in-exception-message.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.