Description
The software’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.
Software 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.
Modes of Introduction:
– Architecture and Design
Related Weaknesses
Consequences
Non-Repudiation: Hide Activities
Potential Mitigations
CVE References
- 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 it 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.
More Stories
The Most Dangerous Vulnerabilities in Apache Tomcat and How to Protect Against Them
Apache Tomcat is an open-source web server and servlet container that is widely used in enterprise environments to run Java...
ZDI-CAN-18333: A Critical Zero-Day Vulnerability in Microsoft Windows
Zero-day vulnerabilities are a serious threat to cybersecurity, as they can be exploited by malicious actors to gain unauthorized access...
CWE-669 – Incorrect Resource Transfer Between Spheres
Description The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere,...
CWE-67 – Improper Handling of Windows Device Names
Description The software constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a...
CWE-670 – Always-Incorrect Control Flow Implementation
Description The code contains a control flow path that does not reflect the algorithm that the path is intended to...
CWE-671 – Lack of Administrator Control over Security
Description The product uses security features in a way that prevents the product's administrator from tailoring security settings to reflect...