Technical Details
- Structure
- Simple
- Vulnerability Mapping
- ALLOWED
Applicable To
Security Consequences
Scope
Impact
Mitigation Strategies
Phase
Description
Perform functionality testing before deploying the application.
Detection Methods
No detection method information available for this CWE.
Code Examples & CVEs
No examples or observed CVEs available for this CWE.
CWE Relationships
No relationship information available for this CWE.
Frequently Asked Questions
What is CWE-447: CWE-447: Unimplemented or Unsupported Feature in UI?+
CWE-447: CWE-447: Unimplemented or Unsupported Feature in UI is a Common Weakness Enumeration (CWE) entry maintained by MITRE. Description
What are the security consequences of CWE-447: Unimplemented or Unsupported Feature in UI?+
If exploited, CWE-447 (CWE-447: Unimplemented or Unsupported Feature in UI) it can compromise Varies by Context and Unexpected State, leading to outcomes such as Scope: Other.
How do you prevent or mitigate CWE-447: Unimplemented or Unsupported Feature in UI?+
Recommended mitigations for CWE-447 include: Perform functionality testing before deploying the application.
Which programming languages are affected by CWE-447: Unimplemented or Unsupported Feature in UI?+
CWE-447 commonly affects Languages. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
What is the difference between a CWE and a CVE?+
A CWE (Common Weakness Enumeration) like CWE-447 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.