View-711: Weaknesses in OWASP Top Ten (2004)

ID: 711

Type: Graph

Status: Obsolete

Objective

CWE nodes in this view (graph) are associated with the OWASP Top Ten, as released in 2004, and as required for compliance with PCI DSS version 1.1. This view is considered obsolete as a newer version of the OWASP Top Ten is available.

Audience

Software Developers

This view outlines the most important issues as identified by the OWASP Top Ten (2004 version), providing a good starting point for web application developers who want to code more securely, as well as complying with PCI DSS 1.1.

Software Customers

This view outlines the most important issues as identified by the OWASP Top Ten, providing customers with a way of asking their software developers to follow minimum expectations for secure code, in compliance with PCI-DSS 1.1.

Educators

Since the OWASP Top Ten covers the most frequently encountered issues, this view can be used by educators as training material for students. However, the 2007 version (CWE-629) might be more appropriate.

Membership

CWE-ID	title
CWE-722	OWASP Top Ten 2004 Category A1 - Unvalidated Input
CWE-723	OWASP Top Ten 2004 Category A2 - Broken Access Control
CWE-724	OWASP Top Ten 2004 Category A3 - Broken Authentication and Session Management
CWE-725	OWASP Top Ten 2004 Category A4 - Cross-Site Scripting (XSS) Flaws
CWE-726	OWASP Top Ten 2004 Category A5 - Buffer Overflows
CWE-727	OWASP Top Ten 2004 Category A6 - Injection Flaws
CWE-728	OWASP Top Ten 2004 Category A7 - Improper Error Handling
CWE-729	OWASP Top Ten 2004 Category A8 - Insecure Storage
CWE-730	OWASP Top Ten 2004 Category A9 - Denial of Service
CWE-731	OWASP Top Ten 2004 Category A10 - Insecure Configuration Management

Notes

Relationship

CWE relationships for this view were obtained by examining the OWASP document and mapping to any items that were specifically mentioned within the text of a category. As a result, this mapping is not complete with respect to all of CWE. In addition, some concepts were mentioned in multiple Top Ten items, which caused them to be mapped to multiple CWE categories. For example, SQL injection is mentioned in both A1 (CWE-722) and A6 (CWE-727) categories.

Maintenance

Some parts of CWE are not fully fleshed out in terms of weaknesses. When these areas were mentioned in the Top Ten, category nodes were mapped, although general mapping practice would usually favor mapping only to weaknesses.

引用

REF-570 Top 10 2004
REF-571 About the PCI Data Security Standard (PCI DSS)

文章来源于互联网:scap中文网