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

Defending Against Unicode Attacks

Master validation strategies including normalization, visual spoofing detection, and safe Unicode handling practices.

Defending Against Unicode Attacks

What you'll learn: How to protect your applications from Unicode-based exploits using normalization, visual spoofing detection, and safe handling practices.

Now that you understand the many ways attackers can weaponize Unicode—from homographs to invisible characters to encoding tricks—it's time to build robust defenses. Think of Unicode defense like airport security: you need multiple layers checking for different threats.

Core Defense Strategies

1. Normalize Before Validating

Always normalize Unicode input to a canonical form (like NFC or NFKC) before validating or comparing it. This prevents attackers from bypassing checks using equivalent but differently-encoded characters.

2. Detect Visual Spoofing

Check for characters from mixed scripts that could enable homograph attacks (like mixing Latin "a" with Cyrillic "а"). Implement confusable character detection—many libraries provide databases of visually similar characters. For critical fields like usernames or domains, restrict to a single script or safe character subset.

3. Strip or Reject Dangerous Characters

Remove or block bidirectional override characters, zero-width characters, and other invisible control sequences unless you have a specific business need for them. These rarely serve legitimate purposes in typical user input.

4. Use Allow Lists

For high-security contexts (passwords, URLs, filenames), prefer strict allow lists of safe characters rather than trying to block every possible Unicode attack vector. It's easier to define what you will accept than to catch every trick.

5. Display with Caution

When rendering Unicode text, especially user-generated content, use proper encoding and consider visual indicators for suspicious patterns (mixed scripts, RTL overrides). Never trust that what users see matches what's actually stored.

6. Length Limits After Normalization

Apply length restrictions after normalization, as combining characters and certain encodings can expand dramatically during normalization.

Key Takeaway: Defend against Unicode attacks by normalizing input early, detecting visual spoofing through script mixing analysis, stripping dangerous control characters, preferring allow lists for critical fields, and never trusting visual appearance alone.