CWE-356: Product UI does not Warn User of Unsafe Actions

BaseIncomplete

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.

View on MITRE
Back to CWE Lookup

Extended Description

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.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-356 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-356, Product UI does not Warn User of Unsafe Actions, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Make elimination of CWE-356 a product outcome

Apply CISA's Secure by Design principle of taking ownership of customer security outcomes to CWE-356, Product UI does not Warn User of Unsafe Actions. Put the weakness in the product threat model and security roadmap, fund class-level design and platform changes, prefer safe defaults and reusable guardrails, and publish measurable progress. Do not transfer the primary burden to customer configuration when the manufacturer can remove or contain the root cause in the product.

Shifting the Balance of Cybersecurity Risk: Secure by Design Software — Cybersecurity and Infrastructure Security Agency

Connect Product UI does not Warn User of Unsafe Actions to documented attack evidence

Recorded impacts include Hide Activities; observed examples include CVE-1999-1055, CVE-1999-0794, and CVE-2000-0277; related weaknesses include CWE-221. Use these source-defined anchors to turn CWE-356 into implementation, review, and verification checks for the affected component.

CWE-356: Product UI does not Warn User of Unsafe Actions — MITRE CWE

Apply precise root-cause mapping to CWE-356

Apply MITRE's full root-cause mapping guidance when using CWE-356, Product UI does not Warn User of Unsafe Actions. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-356 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-356, Product UI does not Warn User of Unsafe Actions. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-356: Product UI does not Warn User of Unsafe Actions?+

CWE-356: Product UI does not Warn User of Unsafe Actions is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Product UI does not Warn User of Unsafe Actions?+

If exploited, CWE-356 (Product UI does not Warn User of Unsafe Actions) it can compromise Non-Repudiation, leading to outcomes such as Hide Activities.

Which programming languages are affected by Product UI does not Warn User of Unsafe Actions?+

CWE-356 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Product UI does not Warn User of Unsafe Actions?+

MITRE documents real CVEs mapped to CWE-356, including CVE-1999-1055, CVE-1999-0794, CVE-2000-0277, CVE-2000-0517 and CVE-2005-0602. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-356 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Find Related CVEs

Search for vulnerabilities that exploit CWE-356

CVE vs CWE: What's the Difference?

Understanding vulnerabilities vs weaknesses

Understanding CVSS Scoring

How vulnerability severity is measured

View Full MITRE Entry

Complete technical details and references

Advertisement