1487
Applicable Platforms
Language : Not Language-Specific (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Access Control
Confidentiality
Availability
Integrity
Other
Bypass Protection Mechanism
Execute Unauthorized Code or Commands
Varies by Context
Potential Mitigations
Phase: Architecture and Design
Strategy = Input Validation
Avoid making decisions based on names of resources (e.g. files) if those resources can have
alternate names.
Phase: Implementation
Strategy = Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use
a list of acceptable inputs that strictly conform to specifications. Reject any input that does not
strictly conform to specifications, or transform it into something that does. When performing
input validation, consider all potentially relevant properties, including length, type of input, the
full range of acceptable values, missing or extra inputs, syntax, consistency across related
fields, and conformance to business rules. As an example of business rule logic, "boat" may be
syntactically valid because it only contains alphanumeric characters, but it is not valid if the input
is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for
malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if
the code's environment changes. This can give attackers enough room to bypass the intended
CWE Version 4.14
CWE-174: Double Decoding of the Same Data
CWE-174: Double Decoding of the Same Data