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.
Potential Impact
Non-Repudiation
Hide Activities
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| CVE-1999-1055 | Product does not warn user when document contains certain dangerous functions or macros. |
| CVE-1999-0794 | Product does not warn user when document contains certain dangerous functions or macros. |
| CVE-2000-0277 | Product does not warn user when document contains certain dangerous functions or macros. |
| CVE-2000-0517 | Product does not warn user about a certificate if it has already been accepted for a different site. Possibly resultant. |
| CVE-2005-0602 | File extractor does not warn user if setuid/setgid files could be extracted. Overlaps privileges/permissions. |
| CVE-2000-0342 | E-mail client allows bypass of warning for dangerous attachments via a Windows .LNK file that refers to the attachment. |
Related Weaknesses
Taxonomy Mappings
- PLOVER: — Product UI does not warn user of unsafe actions
Frequently Asked Questions
What is CWE-356?
CWE-356 (Product UI does not Warn User of Unsafe Actions) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. 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...
How can CWE-356 be exploited?
Attackers can exploit CWE-356 (Product UI does not Warn User of Unsafe Actions) to hide activities. This weakness is typically introduced during the Architecture and Design, Implementation phase of software development.
How do I prevent CWE-356?
Follow secure coding practices, conduct code reviews, and use automated security testing tools (SAST/DAST) to detect this weakness early in the development lifecycle.
What is the severity of CWE-356?
CWE-356 is classified as a Base-level weakness (Medium abstraction). It has been observed in 6 real-world CVEs.