# Usage of Trusted and Untrusted Data inside the same Data Structure

## Overview

* **Rule ID**: `java_lang_trust_boundary_violation`
* **Applicable Languages**: Java
* **Weakness ID**: CWE-501

## Description

Combining trusted and untrusted data within a single data structure presents a serious security risk. This practice can lead to untrusted data being mistakenly treated as reliable, potentially resulting in security vulnerabilities.

## Remediation Guidelines

* **Do not** combine trusted and untrusted data in the same data structure. Keeping them separate ensures that untrusted data does not inadvertently acquire the same level of trust as verified data.

## References

* [**CWE-501: Trust Boundary Violation**](https://cwe.mitre.org/data/definitions/501.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/2-java/usage-of-trusted-and-untrusted-data-inside-the-same-data-structure.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.