1079
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
validation. However, denylists can be useful for detecting potential attacks or determining which
inputs are so malformed that they should be rejected outright.
Phase: Implementation
Strategy = Input Validation
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.
MemberOf Relationships
This MemberOf relationships table shows additional CWE Catgeories and Views that reference this
weakness as a member. This information is often useful in understanding where a weakness fits
within the context of external information sources.
Nature Type ID Name Page
MemberOf 995 SFP Secondary Cluster: Feature 888 2418
MemberOf 1413 Comprehensive Categorization: Protection Mechanism
Failure
1400 2542
Taxonomy Mappings
Mapped Taxonomy Name Node ID Fit Mapped Node Name
PLOVER Multiple Interpretations of UI Input
CWE-451: User Interface (UI) Misrepresentation of Critical Information
Weakness ID : 451
Structure : Simple
Abstraction : Class
Description
The user interface (UI) does not properly represent critical information to the user, allowing the
information - or its source - to be obscured or spoofed. This is often a component in phishing
attacks.
Extended Description
If an attacker can cause the UI to display erroneous data, or to otherwise convince the user to
display information that appears to come from a trusted source, then the attacker could trick the
user into performing the wrong action. This is often a component in phishing attacks, but other
kinds of problems exist. For example, if the UI is used to monitor the security state of a system or
network, then omitting or obscuring an important indicator could prevent the user from detecting
and reacting to a security-critical event.
UI misrepresentation can take many forms:
• Incorrect indicator: incorrect information is displayed, which prevents the user from
understanding the true state of the product or the environment the product is monitoring,
CWE Version 4.14
CWE-451: User Interface (UI) Misrepresentation of Critical Information
CWE-451: User Interface (UI) Misrepresentation of Critical Information