Back to overview

Data validation & encoding 9

Extensive checks and validations can be made of inputs and outputs, but proper actions following the results is what provides security. Data sanitization is a good approach for outputs, as this data is already accepted by the system. Failing input validation always needs to result in rejection. It is also useful to log (associated with the user's identity if possible) and flag these as probably malicious activity for further analysis, or as input for application intrusion detection systems.

NB: Unlike other cards in this suit, VE 9 assumes that input and output validation checks are in place, however they do not correctly respond to incorrect input.

How to play?

Shamun can bypass input validation or output validation checks because validation failures are not rejected and/or sanitized


Owasp ASVS (4.0): 7.1.3

Capec: 28

Owasp SCP: 6,21,22,168

Owasp Appsensor: IE2-3

Safecode: 3,16,24

ASVS (4.0) Cheatsheetseries Index

ASVS V7.1 - Log Content Requirements


SQL Injection

Cross-Site Scripting (XSS)

Command Injection

(Session) Data tampering

Privilege escalation

Loading comments 0%

Github logo View source on GitHub

Provided by dotNET lab

This website is created, hosted and provided by dotNET lab. dotNET lab provides training and guidance on secure software development. Contact us to get in touch!

OWASP Cornucopia

OWASP Cornucopia is originally created by Colin Watson. It is open source and can be downloaded free of charge from the OWASP website. It is is free to use. It is licensed under the Creative Commons Attribution-ShareAlike 3.0 license, so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one. OWASP does not endorse or recommend commercial products or services. OWASP Cornucopia is licensed under the Creative Commons Attribution-ShareAlike 3.0 license and is © 2012-2016 OWASP Foundation.