CWE-178 Improper Handling of Case Sensitivity: Risks and Fixes
When one layer treats .jsp and .JSP as different and another does not, access controls fail. A look at CWE-178 and how to avoid it.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
When one layer treats .jsp and .JSP as different and another does not, access controls fail. A look at CWE-178 and how to avoid it.
Hex encoded input such as %2e%2e can hide path traversal from a filter. How CWE-177 works and how to decode once, then validate.
Unicode input that one layer reads differently from the next can slip past a security check. Here is how CWE-176 happens and what to do about it.
When one input mixes several encodings, filters often handle only one. What CWE-175 means and how to normalize before you validate.
Decode the same input twice and any check between the two steps is useless. How CWE-174 enabled code execution and traversal, and how to fix it.
The same character can be written several valid ways. If your check knows only one, attackers use another. How CWE-173 works and how to fix it.
Double encoding, hex paths and Unicode URLs have exposed source code and allowed traversal. How CWE-172 works and how to decode and validate safely.
A string without its terminating NUL byte makes C functions read or write past the buffer. How CWE-170 happens and how to fix it.
Pairs in the wrong order or special characters that are not nested properly can crash parsers and hide activity. How to find and fix CWE-168.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.