Description
A UI function for a security feature appears to be supported and gives feedback to the user that suggests that it is supported, but the underlying functionality is not implemented.
Potential Impact
Other
Varies by Context, Unexpected State
Mitigations & Prevention
Perform functionality testing before deploying the application.
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| CVE-2000-0127 | GUI configuration tool does not enable a security option when a checkbox is selected, although that option is honored when manually set in the configuration file. |
| CVE-2001-0863 | Router does not implement a specific keyword when it is used in an ACL, allowing filter bypass. |
| CVE-2001-0865 | Router does not implement a specific keyword when it is used in an ACL, allowing filter bypass. |
| CVE-2004-0979 | Web browser does not properly modify security setting when the user sets it. |
Related Weaknesses
Taxonomy Mappings
- PLOVER: — Unimplemented or unsupported feature in UI
Frequently Asked Questions
What is CWE-447?
CWE-447 (Unimplemented or Unsupported Feature in UI) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. A UI function for a security feature appears to be supported and gives feedback to the user that suggests that it is supported, but the underlying functionality is not implemented.
How can CWE-447 be exploited?
Attackers can exploit CWE-447 (Unimplemented or Unsupported Feature in UI) to varies by context, unexpected state. This weakness is typically introduced during the Implementation phase of software development.
How do I prevent CWE-447?
Key mitigations include: Perform functionality testing before deploying the application.
What is the severity of CWE-447?
CWE-447 is classified as a Base-level weakness (Medium abstraction). It has been observed in 4 real-world CVEs.