The CWE/SANS released the following list of most dangerous programming errors. This is not limited to Microsoft technologies but can be applied to any programming language used today. The document was released February 17 and is both available in PDF and in plain html. The errors can be categorized in three sections:
- Insecure interaction between components (insecure ways in which data is sent and received between components)
- Risky resource management (bad management of important system resources)
- Porous Defenses (misusing/abusing/ignoring defensive techniques)
The list of errors:
- Failure to Preserve Web Page Structure ('Cross-site Scripting')
- Improper Sanitization of Special Elements used in an SQL Command ('SQL Injection')
- Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
- Cross-Site Request Forgery (CSRF)
- Improper Access Control (Authorization)
- Reliance on Untrusted Inputs in a Security Decision
- Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- Unrestricted Upload of File with Dangerous Type
- Improper Sanitization of Special Elements used in an OS Command ('OS Command Injection')
- Missing Encryption of Sensitive Data
- Use of Hard-coded Credentials
- Buffer Access with Incorrect Length Value
- Improper Control of Filename for Include/Require Statement in PHP Program ('PHP File Inclusion')
- Improper Validation of Array Index
- Improper Check for Unusual or Exceptional Conditions
- Information Exposure Through an Error Message
- Integer Overflow or Wraparound
- Incorrect Calculation of Buffer Size
- Missing Authentication for Critical Function
- Download of Code Without Integrity Check
- Incorrect Permission Assignment for Critical Resource
- Allocation of Resources Without Limits or Throttling
- URL Redirection to Untrusted Site ('Open Redirect')
- Use of a Broken or Risky Cryptographic Algorithm
- Race Condition
Full article: HTML - PDF