CWEweakness
CWE-637 Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism')
- Alternate terms
- Unnecessary Complexity
- Abstraction
- Class
- Structure
- Simple
- Status
- Draft
- Languages
- Not Language-Specific
- CWE version
- 5.0
Description
The product uses a more complex mechanism than necessary, which could lead to resultant weaknesses when the mechanism is not correctly understood, modeled, configured, implemented, or used.
Common consequences
• Other: Other
Potential mitigations
• [Architecture and Design] Security mechanisms should be as simple as possible. Complex security mechanisms may engender partial implementations and compatibility problems, with resulting mismatches in assumptions and implemented security. Avoid complex security mechanisms when simpler ones would meet requirements. Avoid complex data models, and unnecessarily complex operations. Adopt architectures that provide guarantees, simplify understanding through elegance and abstraction, and that can be implemented similarly. Modularize, isolate and do not trust complex code, and apply other secure programming principles on these modules (e.g., least privilege) to mitigate vulnerabilities.
• [Requirements] Data specifications should be as simple as possible, because complex data specifications result in complex validation code. Complex tasks and systems may also need to be guarded by complex security checks, so simple systems should be preferred.
Observed examples
• CVE-2007-6067: Support for complex regular expressions leads to a resultant algorithmic complexity weakness (CWE-407).
• CVE-2007-1552: Either a filename extension and a Content-Type header could be used to infer the file type, but the developer only checks the Content-Type, enabling unrestricted file upload (CWE-434).
• CVE-2007-6479: In Apache environments, a "filename.php.gif" can be redirected to the PHP interpreter instead of being sent as an image/gif directly to the user. Not knowing this, the developer only checks the last extension of a submitted filename, enabling arbitrary code execution.
• CVE-2005-2148: The developer cleanses the $_REQUEST superglobal array, but PHP also populates $_GET, allowing attackers to bypass the protection mechanism and conduct SQL injection attacks against code that uses $_GET.
Related
Observed example · CVE (4)
- CVE-2007-6067 Algorithmic complexity vulnerability in the regular expression parser in TCL before 8.4.17, as used in PostgreSQL 8.2 before 8.2.6, 8.1… vulnerability
- CVE-2007-6479 Unrestricted file upload vulnerability in the "My productions" component for main/auth/profile.php (aka the "My profile" page) in Dokeos… vulnerability
- CVE-2007-1552 Unrestricted file upload vulnerability in usercp.php in MetaForum 0.513 Beta restricts file types based on the MIME type in the… vulnerability
- CVE-2005-2148 Cacti 0.8.6e and earlier does not perform proper input validation to protect against common attacks, which allows remote attackers to… vulnerability
Child of · CWE (1)
- CWE-657 Violation of Secure Design Principles weakness
Referenced by CVE · weakness (1)
- CVE-2026-9058 For untrusted certificates that contain the "Authority Information Access - caIssuers URI" extension, Szafir SDK will automatically… vulnerability