The OWASP Source Code Flaws Top 10

C1 - Design Weakness	A design weakness occurs when your business logic isn't strong enough to a threat modeling activity so it may be easy for an attacker to subvert your application behavior. Design is also about objects scope and visibility so extra care must be taken to what your program expose to others.
C2 - Architectural Weakness	Your application at runtime is not a standalone part of the entire world, it depends over auxiliary system. An architectural weakness occurs when your code interact in a non safe way to auxiliary systems.
C3 - Missing input validation	A
C4 - Insecure communications	A
C5 - Information leakage and improper error handling	A
C6 - Direct object reference	A
C7 - Misuse of local resources	A
C8 - Usage of potentially dangerous APIs	A
C9 - Documentation weakness	A
C10 - Best practices violation	A

Table 1: Top 10 Source code flaws for 2009

This category currently contains no pages or media.

Category:OWASP Source Code Flaws Top 10 Project Index