Product UI does not Warn User of Unsafe Actions
Incomplete Base
Structure: Simple
Description
The product's user interface does not warn the user before undertaking an unsafe action on behalf of that user. This makes it easier for attackers to trick users into inflicting damage to their system.
Product systems should warn users that a potentially dangerous action may occur if the user proceeds. For example, if the user downloads a file from an unknown source and attempts to execute the file on their machine, then the application's GUI can indicate that the file is unsafe.
Common Consequences 1
Scope: Non-Repudiation
Impact: Hide Activities
Observed Examples 6
CVE-1999-1055Product does not warn user when document contains certain dangerous functions or macros.
CVE-1999-0794Product does not warn user when document contains certain dangerous functions or macros.
CVE-2000-0277Product does not warn user when document contains certain dangerous functions or macros.
CVE-2000-0517Product does not warn user about a certificate if it has already been accepted for a different site. Possibly resultant.
CVE-2005-0602File extractor does not warn user if setuid/setgid files could be extracted. Overlaps privileges/permissions.
CVE-2000-0342E-mail client allows bypass of warning for dangerous attachments via a Windows .LNK file that refers to the attachment.
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Modes of Introduction
Architecture and Design
Implementation
Related Weaknesses
Taxonomy Mapping
- PLOVER
Notes
RelationshipOften resultant, e.g. in unhandled error conditions.
RelationshipCan overlap privilege errors, conceptually at least.