BaseDraft

CWE-501Trust Boundary Violation

Category: other

Description

The product mixes trusted and untrusted data in the same data structure or structured message. A trust boundary can be thought of as line drawn through a program. On one side of the line, data is untrusted. On the other side of the line, data is assumed to be trustworthy. The purpose of validation logic is to allow data to safely cross the trust boundary - to move from untrusted to trusted. A trust boundary violation occurs when a program blurs the line between what is trusted and what is untrusted. By combining trusted and untrusted data in the same data structure, it becomes easier for programmers to mistakenly trust unvalidated data.

Common consequences· 1

  • Access Control — Bypass Protection Mechanism

References

  1. https://cwe.mitre.org/data/definitions/501.html

(incoming)4

TypeTargetConfidenceTier
VulnerabilityCVE-2025-48938cve-2025-489380%live
VulnerabilityOracle E-Business Suite Server-Side Request Forgery (SSRF) Vulnerabilitycve-2025-618840%live
VulnerabilityCVE-2025-64496cve-2025-644960%live
VulnerabilityCVE-2026-25725cve-2026-257250%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Deserialization of Untrusted Data
CWE
Insufficient Verification of Data Authenticity
CWE
Acceptance of Extraneous Untrusted Data With Trusted Data
CWE
Violation of Secure Design Principles
CWE
Improper Input Validation
CWE
Improper Enforcement of Message Integrity During Transmission in a Communication Channel
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.