Improper Handling of Mixed Encoding

The product does not properly handle when the same input uses several different (mixed) encodings.

We track 1 vulnerability of this type. 100% are rated high or critical, and the average CVSS score is 9.8.

How this weakness is prevented

• Architecture and Design: Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
• Implementation: Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.