CWE-327
Use of a Broken or Risky Cryptographic Algorithm
The product uses a broken or risky cryptographic algorithm or protocol.
Abstraction
Class
Structure
Simple
Likelihood of Exploit
High
Understand the problem
What is the problem?
Extended description
Root cause
How and when does the problem arise?
Lifecycle phase
Architecture and Design
Lifecycle phase
Implementation
Risk
What does successful exploitation lead to?
Affected security scopes: Confidentiality
Affected security scopes: Integrity
Affected security scopes: Accountability, Non-Repudiation
Defence
How is it prevented and fixed?
Architecture and Design
Libraries or Frameworks
Detail
Architecture and Design
Libraries or Frameworks
Architecture and Design
Architecture and design approach
Detail
Architecture and Design
Architecture and design approach
Effectiveness: Defense in Depth
Architecture and Design
Architecture and design approach
Detail
Architecture and Design
Architecture and design approach
Architecture and Design
Libraries or Frameworks
Detail
Architecture and Design
Libraries or Frameworks
Implementation · Architecture and Design
Defence to apply across several lifecycle phases
Detail
Implementation · Architecture and Design
Defence to apply across several lifecycle phases
Verification
How is it detected?
Automated Analysis
ModerateFalse negatives may occur if the tool is not aware of the cryptographic libraries in use, or if custom cryptography is being used.
Manual Analysis
These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.