This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Testing for Input Validation"
(→Data Validation Testing) |
(→Data Validation Testing) |
||
| Line 6: | Line 6: | ||
The most common web application security weakness is the failure to properly validate input from the client or environment. This weakness leads to almost all of the major vulnerabilities in applications, such as interpreter injection, locale/Unicode attacks, file system attacks and buffer overflows.<br> | The most common web application security weakness is the failure to properly validate input from the client or environment. This weakness leads to almost all of the major vulnerabilities in applications, such as interpreter injection, locale/Unicode attacks, file system attacks and buffer overflows.<br> | ||
| − | Data from the client should never be trusted for the client has every possibility to tamper with the data: "All Input is Evil" | + | Data from the client should never be trusted for the client has every possibility to tamper with the data: "All Input is Evil" says Michael Howard in his famous book "Writing Secure Code". That's rule number one. The problem is that in a complex application the points of access for an attacker increase and it is easy that you forget to implement this rule. |
<br> | <br> | ||
In this chapter we describe how to test all the possible forms of input validation to understand if the application is strong enough against any type of data input.<br> | In this chapter we describe how to test all the possible forms of input validation to understand if the application is strong enough against any type of data input.<br> | ||
Revision as of 16:00, 7 November 2006
[Up]
OWASP Testing Guide v2 Table of Contents
Data Validation Testing
The most common web application security weakness is the failure to properly validate input from the client or environment. This weakness leads to almost all of the major vulnerabilities in applications, such as interpreter injection, locale/Unicode attacks, file system attacks and buffer overflows.
Data from the client should never be trusted for the client has every possibility to tamper with the data: "All Input is Evil" says Michael Howard in his famous book "Writing Secure Code". That's rule number one. The problem is that in a complex application the points of access for an attacker increase and it is easy that you forget to implement this rule.
In this chapter we describe how to test all the possible forms of input validation to understand if the application is strong enough against any type of data input.
We split Data Validation into this macro categories:
Input -> Output == cross-site scripting
4.6.1 Cross site scripting
Input -> HTTP Methods == XST
4.6.1.1 HTTP Methods and XST
Input -> Query SQL == SQL injection
4.6.2 SQL Injection
4.6.2.1 Stored procedure injection
4.6.2.2 Oracle Testing
4.6.2.3 MySQL Testing
4.6.2.4 SQL Server Testing
Input -> Query LDAP == LDAP injection
4.6.4 LDAP Injection
Input -> System == command injection
4.6.3 ORM Injection
4.6.5 XML Injection
4.6.6 SSI Injection
4.6.7 XPath Injection
4.6.8 IMAP/SMTP Injection
4.6.9 Code Injection
4.6.10 OS Commanding
Input -> Fixed buffer or format string == overflow
4.6.11 Buffer overflow Testing
4.6.11.1 Heap overflow
4.6.11.2 Stack overflow
4.6.11.3 Format string
4.6.12 Incubated vulnerability testing
Incubated testing is a complex testing that need more that one data valition vulnerability to work.
In every pattern showed the data must be validated from the application before trust it and execute it. Our goal is to test if the application really do that.
