1446
[REF-544]Sean Barnum and Michael Gegick. "Never Assuming that Your Secrets Are Safe". 2005
September 4. < https://web.archive.org/web/20220126060054/https://www.cisa.gov/uscert/bsi/
articles/knowledge/principles/never-assuming-that-your-secrets-are-safe >.2023-04-07.
[REF-542]Jon Postel, Editor. "RFC: 793, TRANSMISSION CONTROL PROTOCOL". 1981
September. Information Sciences Institute. < https://www.ietf.org/rfc/rfc0793.txt >.2023-04-07.
CWE-657: Violation of Secure Design Principles
Weakness ID : 657
Structure : Simple
Abstraction : Class
Description
The product violates well-established principles for secure design.
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 resourceintensive
to fix design problems.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 710 Improper Adherence to Coding Standards 1549
ParentOf 250 Execution with Unnecessary Privileges 599
ParentOf 636 Not Failing Securely ('Failing Open') 1401
ParentOf 637 Unnecessary Complexity in Protection Mechanism (Not
Using 'Economy of Mechanism')