Multiple Interpretations of UI Input

The UI has multiple interpretations of user input but does not prompt the user when it selects the less secure interpretation.

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

How this weakness is prevented

• 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.