CWE•Variant•Draft•3 recent CVEs
CWE-173Improper Handling of Alternate Encoding
Description
The product does not properly handle when an input uses an alternate encoding that is valid for the control sphere to which the input is being sent.
Common consequences
- Access Control→Bypass Protection Mechanism
Potential mitigations
- Architecture and DesignAvoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
- Implementation[object Object]
- ImplementationUse and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are i
- ImplementationInputs 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.