2010 Top 25 - Porous Defenses |
| Category ID: 803 (Category) | Status: Incomplete |
Description Relationships| Nature | Type | ID | Name | View(s) this relationship pertains to |
|---|---|---|---|---|
| ParentOf |  Weakness Class | 285 | Improper Access Control (Authorization) | Weaknesses in the 2010 CWE/SANS Top 25 Most Dangerous Programming Errors (primary)800 |
| ParentOf |  Weakness Variant | 306 | Missing Authentication for Critical Function | Weaknesses in the 2010 CWE/SANS Top 25 Most Dangerous Programming Errors (primary)800 |
| ParentOf |  Weakness Base | 311 | Missing SecurityDatabase\Encrypt\Encryption of Sensitive Data | Weaknesses in the 2010 CWE/SANS Top 25 Most Dangerous Programming Errors (primary)800 |
| ParentOf | Weakness Base | 327 | Use of a Broken or Risky Cryptographic Algorithm | Weaknesses in the 2010 CWE/SANS Top 25 Most Dangerous Programming Errors (primary)800 |
| ParentOf | Weakness Class | 732 | Incorrect Permission Assignment for Critical Resource | Weaknesses in the 2010 CWE/SANS Top 25 Most Dangerous Programming Errors (primary)800 |
| ParentOf | Weakness Base | 798 | Use of Hard-coded Credentials | Weaknesses in the 2010 CWE/SANS Top 25 Most Dangerous Programming Errors (primary)800 |
| ParentOf | Weakness Base | 807 | Reliance on Untrusted Inputs in a Security Decision | Weaknesses in the 2010 CWE/SANS Top 25 Most Dangerous Programming Errors (primary)800 |
| MemberOf | View | 800 | Weaknesses in the 2010 CWE/SANS Top 25 Most Dangerous Programming Errors | Weaknesses in the 2010 CWE/SANS Top 25 Most Dangerous Programming Errors (primary)800 |
References Content History
