Insufficient UI Warning of Dangerous Operations

Draft Base
Structure: Simple
Description

This vulnerability occurs when a software application does present a warning to a user before a risky action, but the warning is designed or placed in a way that makes it too easy to miss, ignore, or accidentally dismiss.

Extended Description

Effective security warnings must actively capture user attention to be useful. A warning that is subtle, buried in other text, uses unclear language, or can be dismissed with a single click fails its primary purpose. This often happens when designers prioritize a clean user interface over security communication, or when warnings become so frequent that users habitually click through them—a phenomenon known as 'warning fatigue.' The core risk is that users may unintentionally perform dangerous operations like deleting critical data, overwriting files, or granting excessive permissions. To prevent this, warnings should be prominent, require a deliberate action to acknowledge (like typing a confirmation word), and clearly explain the consequences. For developers, this means implementing modal dialogs for critical actions, using contrasting colors and icons, and avoiding pre-selected 'OK' buttons to force conscious user interaction.

Common Consequences 1
Scope: Non-Repudiation

Impact: Hide Activities

Observed Examples 1
CVE-2007-1099User not sufficiently warned if host key mismatch occurs
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Modes of Introduction
Architecture and Design
Implementation
Related Weaknesses
Taxonomy Mapping
  • PLOVER