Course contentsShow
← Security
Lesson 1157 of 3,05224. Application Security - Input ValidationFree lesson

Common Input Validation Pitfalls

Recognize common mistakes like client-side only validation, incomplete checks, and double validation errors.

Common Input Validation Pitfalls

What you'll learn: The most frequent mistakes developers make when implementing input validation—and how attackers exploit them.

Even with the best intentions, validation logic often contains critical flaws. Understanding these common pitfalls helps you avoid repeating them in your own applications.

Client-Side Only Validation

The most dangerous mistake is validating input only in the browser. JavaScript checks stop honest users from making mistakes, but attackers bypass them trivially by crafting direct HTTP requests or using browser developer tools. Client-side validation is a UX feature, not a security control.

Analogy: It's like having a bouncer who only checks IDs at the front door while leaving the back entrance wide open.

Incomplete Checks

Validation that covers only part of the attack surface fails. Examples include:

  • Checking for <script> tags but missing <img onerror=...>
  • Blocking ../ but allowing URL-encoded %2e%2e%2f
  • Validating string length but ignoring multibyte characters that expand after processing
  • Allowing valid types (like integers) without checking ranges or business rules

Double Validation Errors

When multiple layers validate the same input differently, inconsistencies create vulnerabilities:

  • The application gateway blocks '; DROP TABLE but the backend accepts it after URL decoding
  • One component strips <script> while another processes it differently
  • Validation functions disagree on what constitutes valid input

This often happens when validation logic is duplicated rather than centralized.

Other Common Mistakes

  • Validating after transformations: Checking input, then converting encoding/format afterward
  • Trusting internal data: Assuming data from databases or APIs is safe
  • Insufficient error messages: Revealing system details in validation failures

Key Takeaway: Always validate on the server, check comprehensively against all attack vectors, maintain consistent validation logic across layers, and never trust data from any source—including your own client code.