CWE-657: Violation of Secure Design Principles

ClassDraft

The product violates well-established principles for secure design.

View on MITRE
Back to CWE Lookup

Extended Description

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.

Technical Details

Structure
Simple

Applicable To

Languages
Platforms

Frequently Asked Questions

What is CWE-657: Violation of Secure Design Principles?+

CWE-657: Violation of Secure Design Principles is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Violation of Secure Design Principles?+

If exploited, CWE-657 (Violation of Secure Design Principles) it can compromise Other, leading to outcomes such as Other.

What are real-world examples of Violation of Secure Design Principles?+

MITRE documents real CVEs mapped to CWE-657, including CVE-2019-6260, CVE-2007-5277, CVE-2006-7142 and CVE-2007-0408. 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-657 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