CWE-657: Violation of Secure Design Principles
Description
The product violates well-established principles for secure design.
This can introduce resultant weaknesses or make it easier for developers to introduce related weaknesses during implementation. Because code is centered around design, it can be resource-intensive to fix design problems.
- Abstraction
- ClassAn abstract weakness, independent of any specific language or technology.
- Likelihood of exploit
- Not rated by MITRE
- Status
- Draft
Common consequences
- Other
Other
Related weaknesses
Parent weaknesses
Child weaknesses
- CWE-250Execution with Unnecessary Privileges
- CWE-636Not Failing Securely ('Failing Open')
- CWE-637Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism')
- CWE-638Not Using Complete Mediation
- CWE-653Improper Isolation or Compartmentalization
- CWE-654Reliance on a Single Factor in a Security Decision
- CWE-655Insufficient Psychological Acceptability
- CWE-656Reliance on Security Through Obscurity
- CWE-671Lack of Administrator Control over Security
- CWE-1192Improper Identifier for IP Block used in System-On-Chip (SOC)
- CWE-1395Dependency on Vulnerable Third-Party Component
CAPEC attack patterns that exploit it
CWE 4.20 links no CAPEC attack pattern to this weakness.