Difference between revisions of "Trust Boundary Violation"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
 
{{Template:Vulnerability}}
 
{{Template:Vulnerability}}
 
{{Template:Fortify}}
 
{{Template:Fortify}}
 
+
<br>
__TOC__
+
 
+
 
[[ASDR Table of Contents]]
 
[[ASDR Table of Contents]]
  
  
 
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
 
 
  
 
==Description==
 
==Description==
 
 
Commingling trusted and untrusted data in the same data structure encourages programmers to mistakenly trust unvalidated data.
 
Commingling trusted and untrusted data in the same data structure encourages programmers to mistakenly trust unvalidated data.
  
Line 19: Line 13:
  
 
A trust boundary violation occurs when a program blurs the line between what is trusted and what is untrusted. The most common way to make this mistake is to allow trusted and untrusted data to commingle in the same data structure.
 
A trust boundary violation occurs when a program blurs the line between what is trusted and what is untrusted. The most common way to make this mistake is to allow trusted and untrusted data to commingle in the same data structure.
 
  
  

Revision as of 08:59, 19 February 2009

This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.


This article includes content generously donated to OWASP by Fortify.JPG.


ASDR Table of Contents


Last revision (mm/dd/yy): 02/19/2009

Description

Commingling trusted and untrusted data in the same data structure encourages programmers to mistakenly trust unvalidated data.

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. The most common way to make this mistake is to allow trusted and untrusted data to commingle in the same data structure.


Risk Factors

  • Talk about the factors that make this vulnerability likely or unlikely to actually happen
  • Discuss the technical impact of a successful exploit of this vulnerability
  • Consider the likely [business impacts] of a successful attack


Examples

The following Java code accepts an HTTP request and stores the usrname parameter in the HTTP session object before checking to ensure that the user has been authenticated.

  usrname = request.getParameter("usrname");
  if (session.getAttribute(ATTR_USR) == null) {
      session.setAttribute(ATTR_USR, usrname);
  }

Without well-established and maintained trust boundaries, programmers will inevitably lose track of which pieces of data have been validated and which have not. This confusion will eventually allow some data to be used without first being validated.


Related Attacks


Related Vulnerabilities


Related Controls

Related Technical Impacts


References

TBD