Description
The software does not properly handle when an input contains Unicode encoding.
Modes of Introduction:
– Implementation
Related Weaknesses
CWE-172
Consequences
Integrity: Unexpected State
Potential Mitigations
Phase: Architecture and Design
Description:
Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
Phase: Implementation
Description:
Phase: Implementation
Description:
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.
CVE References
- CVE-2000-0884
- Server allows remote attackers to read documents outside of the web root, and possibly execute arbitrary commands, via malformed URLs that contain Unicode encoded characters.
- CVE-2001-0709
- Server allows a remote attacker to obtain source code of ASP files via a URL encoded with Unicode.
