Is a method used to gain access to data systems or networks primarily through misrepresentation?

Weakness ID: 451

Abstraction: Class
Structure: Simple

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 software or the environment the software is monitoring, especially of potentially-dangerous conditions or operations. This can be broken down into several different subtypes.
  • Overlay: an area of the display is intended to give critical information, but another process can modify the display by overlaying another element on top of it. The user is not interacting with the expected portion of the user interface. This is the problem that enables clickjacking attacks, although many other types of attacks exist that involve overlay.
  • Icon manipulation: the wrong icon, or the wrong color indicator, can be influenced [such as making a dangerous .EXE executable look like a harmless .GIF]
  • Timing: the software is performing a state transition or context switch that is presented to the user with an indicator, but a race condition can cause the wrong indicator to be used before the product has fully switched context. The race window could be extended indefinitely if the attacker can trigger an error.
  • Visual truncation: important information could be truncated from the display, such as a long filename with a dangerous extension that is not displayed in the GUI because the malicious portion is truncated. The use of excessive whitespace can also cause truncation, or place the potentially-dangerous indicator outside of the user's field of view [e.g. "filename.txt .exe"]. A different type of truncation can occur when a portion of the information is removed due to reasons other than length, such as the accidental insertion of an end-of-input marker in the middle of an input, such as a NUL byte in a C-style string.
  • Visual distinction: visual information might be presented in a way that makes it difficult for the user to quickly and correctly distinguish between critical and unimportant segments of the display.
  • Homographs: letters from different character sets, fonts, or languages can appear very similar [i.e. may be visually equivalent] in a way that causes the human user to misread the text [for example, to conduct phishing attacks to trick a user into visiting a malicious web site with a visually-similar name as a trusted site]. This can be regarded as a type of visual distinction issue.

Relationships

This table shows the weaknesses and high level categories that are related to this weakness. These relationships are defined as ChildOf, ParentOf, MemberOf and give insight to similar items that may exist at higher and lower levels of abstraction. In addition, relationships such as PeerOf and CanAlsoBe are defined to show similar weaknesses that the user may want to explore.

Relevant to the view "Research Concepts" [CWE-1000]

NatureTypeIDName
ChildOf
Class - a weakness that is described in a very abstract fashion, typically independent of any specific language or technology. More specific than a Pillar Weakness, but more general than a Base Weakness. Class level weaknesses typically describe issues in terms of 1 or 2 of the following dimensions: behavior, property, and resource.
221 Information Loss or Omission
ChildOf
Class - a weakness that is described in a very abstract fashion, typically independent of any specific language or technology. More specific than a Pillar Weakness, but more general than a Base Weakness. Class level weaknesses typically describe issues in terms of 1 or 2 of the following dimensions: behavior, property, and resource.
684 Incorrect Provision of Specified Functionality
ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
1007 Insufficient Visual Distinction of Homoglyphs Presented to User
ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
1021 Improper Restriction of Rendered UI Layers or Frames
PeerOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
346 Origin Validation Error

Modes Of Introduction

The different Modes of Introduction provide information about how and when this weakness may be introduced. The Phase identifies a point in the life cycle at which introduction may occur, while the Note provides a typical scenario related to introduction during the given phase.

PhaseNote
Architecture and Design
Implementation

Applicable Platforms

This listing shows possible areas for which the given weakness could appear. These may be for specific named Languages, Operating Systems, Architectures, Paradigms, Technologies, or a class of such platforms. The platform is listed along with how frequently the given weakness appears for that instance.

Languages

Class: Language-Independent [Undetermined Prevalence]

Common Consequences

This table specifies different individual consequences associated with the weakness. The Scope identifies the application security area that is violated, while the Impact describes the negative technical impact that arises if an adversary succeeds in exploiting this weakness. The Likelihood provides information about how likely the specific consequence is expected to be seen relative to the other consequences in the list. For example, there may be high likelihood that a weakness will be exploited to achieve a certain impact, but a low likelihood that it will be exploited to achieve a different impact.

ScopeImpactLikelihood
Non-Repudiation
Access Control

Technical Impact: Hide Activities; Bypass Protection Mechanism

Observed Examples

ReferenceDescription

CVE-2004-2227

Web browser's filename selection dialog only shows the beginning portion of long filenames, which can trick users into launching executables with dangerous extensions.

CVE-2001-0398

Attachment with many spaces in filename bypasses "dangerous content" warning and uses different icon. Likely resultant.

CVE-2001-0643

Misrepresentation and equivalence issue.

CVE-2005-0593

Lock spoofing from several different weaknesses.

CVE-2004-1104

Incorrect indicator: web browser can be tricked into presenting the wrong URL

CVE-2005-0143

Incorrect indicator: Lock icon displayed when an insecure page loads a binary file loaded from a trusted site.

CVE-2005-0144

Incorrect indicator: Secure "lock" icon is presented for one channel, while an insecure page is being simultaneously loaded in another channel.

CVE-2004-0761

Incorrect indicator: Certain redirect sequences cause security lock icon to appear in web browser, even when page is not encrypted.

CVE-2004-2219

Incorrect indicator: Spoofing via multi-step attack that causes incorrect information to be displayed in browser address bar.

CVE-2004-0537

Overlay: Wide "favorites" icon can overlay and obscure address bar

CVE-2005-2271

Visual distinction: Web browsers do not clearly associate a Javascript dialog box with the web page that generated it, allowing spoof of the source of the dialog. "origin validation error" of a sort?

CVE-2005-2272

Visual distinction: Web browsers do not clearly associate a Javascript dialog box with the web page that generated it, allowing spoof of the source of the dialog. "origin validation error" of a sort?

CVE-2005-2273

Visual distinction: Web browsers do not clearly associate a Javascript dialog box with the web page that generated it, allowing spoof of the source of the dialog. "origin validation error" of a sort?

CVE-2005-2274

Visual distinction: Web browsers do not clearly associate a Javascript dialog box with the web page that generated it, allowing spoof of the source of the dialog. "origin validation error" of a sort?

CVE-2001-1410

Visual distinction: Browser allows attackers to create chromeless windows and spoof victim's display using unprotected Javascript method.

CVE-2002-0197

Visual distinction: Chat client allows remote attackers to spoof encrypted, trusted messages with lines that begin with a special sequence, which makes the message appear legitimate.

CVE-2005-0831

Visual distinction: Product allows spoofing names of other users by registering with a username containing hex-encoded characters.

CVE-2003-1025

Visual truncation: Special character in URL causes web browser to truncate the user portion of the "user@domain" URL, hiding real domain in the address bar.

CVE-2005-0243

Visual truncation: Chat client does not display long filenames in file dialog boxes, allowing dangerous extensions via manipulations including [1] many spaces and [2] multiple file extensions.

CVE-2005-1575

Visual truncation: Web browser file download type can be hidden using whitespace.

CVE-2004-2530

Visual truncation: Visual truncation in chat client using whitespace to hide dangerous file extension.

CVE-2005-0590

Visual truncation: Dialog box in web browser allows user to spoof the hostname via a long "user:pass" sequence in the URL, which appears before the real hostname.

CVE-2004-1451

Visual truncation: Null character in URL prevents entire URL from being displayed in web browser.

CVE-2004-2258

Miscellaneous -- [step-based attack, GUI] -- Password-protected tab can be bypassed by switching to another tab, then back to original tab.

CVE-2005-1678

Miscellaneous -- Dangerous file extensions not displayed.

CVE-2002-0722

Miscellaneous -- Web browser allows remote attackers to misrepresent the source of a file in the File Download dialog box.

Potential Mitigations

Phase: Implementation

Strategy: Input Validation

Perform data validation [e.g. syntax, length, etc.] before interpreting the data.

Phase: Architecture and Design

Strategy: Output Encoding

Create a strategy for presenting information, and plan for how to display unusual characters.

Memberships

This MemberOf Relationships table shows additional CWE Categories 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.

Notes

Maintenance

This entry should be broken down into more precise entries. See extended description.

Research Gap

Misrepresentation problems are frequently studied in web browsers, but there are no known efforts for classifying these kinds of problems in terms of the shortcomings of the interface. In addition, many misrepresentation issues are resultant.

Taxonomy Mappings

Mapped Taxonomy NameNode IDFitMapped Node Name
PLOVER UI Misrepresentation of Critical Information

References

Content History

SubmissionsSubmission DateSubmitterOrganization
ModificationsModification DateModifierOrganization
Previous Entry NamesChange DatePrevious Entry Name
2006-07-19 PLOVER
2008-07-01 Eric Dalci Cigital
updated Potential_Mitigations, Time_of_Introduction
2008-09-08 CWE Content Team MITRE
updated Maintenance_Notes, Relationships, Other_Notes, Taxonomy_Mappings
2011-06-01 CWE Content Team MITRE
updated Common_Consequences
2012-05-11 CWE Content Team MITRE
updated Relationships
2012-10-30 CWE Content Team MITRE
updated Potential_Mitigations
2014-02-13 CWE Content Team MITRE
Defined several different subtypes of this issue.
2014-02-18 CWE Content Team MITRE
updated Applicable_Platforms, Description, Maintenance_Notes, Name, Observed_Examples, Other_Notes, References, Relationships, Research_Gaps
2014-07-30 CWE Content Team MITRE
updated Relationships
2017-01-19 CWE Content Team MITRE
updated Relationships
2017-11-08 CWE Content Team MITRE
updated Observed_Examples, References, Relationships, Type
2020-02-24 CWE Content Team MITRE
updated Relationships
2021-03-15 CWE Content Team MITRE
updated Maintenance_Notes, Observed_Examples
2021-10-28 CWE Content Team MITRE
updated Relationships
2022-04-28 CWE Content Team MITRE
updated Relationships
2014-02-18 UI Misrepresentation of Critical Information

More information is available — Please select a different filter.

Which of the following deals with keeping information networks and systems secure from unauthorized access?

Cybersecurity is the protection of internet-connected systems such as hardware, software and data from cyberthreats. The practice is used by individuals and enterprises to protect against unauthorized access to data centers and other computerized systems.

Which type of network traffic originates from outside the network routers and proceeds toward a destination inside the network?

Ingress traffic is network traffic that originates from outside of the network's routers and proceeds toward a destination inside of the network.

What security term defines what resources can be accessed and used?

Access control is a security technique that regulates who or what can view or use resources in a computing environment. It is a fundamental concept in security that minimizes risk to the business or organization.

What is required for highly secure?

We have identified seven necessary properties of highly secure, network-connected devices: a hardware-based root of trust, a small trusted computing base, defense in depth, compartmentalization, certificate-based authentication, security renewal, and failure reporting [in Section 2].

Chủ Đề