Trusted SF Member
Joined: 26 Jul 2002
|Posted: Tue Jan 14, 2003 6:44 pm Post subject: Application Security Project - How to Code Securely
The Open Web Application Security Project (OWASP) has released their Top Ten List of Dumb Programmer Mistakes in order to help organizations understand and improve the security of their web applications and web services. This list was created to focus government and industry on the most serious of these vulnerabilities. Web application security vulnerabilities are highly exploitable and the consequence of an attack can be devastating. These vulnerabilities represent an equivalent magnitude of risk as network security problems, and should be given the same degree of attention.
Using this list, organizations can send a message to web site developers that "we want you to make sure that you won't make these mistakes." The security issues raised here are not new. In fact, some have been well understood for decades. Yet for some reason, major software development projects are still making these mistakes and jeopardizing not only their customersí security, but also the security of the entire Internet.
1 - Unvalidated Parameters - Information from web requests is not validated before being used by a web application. Attackers can use these flaws to attack backside components through a web application.
2 - Broken Access Control - Restrictions on what authenticated users are allowed to do are not properly enforced. Attackers can exploit these flaws to access other usersí accounts, view sensitive files, or use unauthorized functions.
3 - Broken Account and Session Management - Account credentials and session tokens are not properly protected. Attackers that can compromise passwords, keys, session cookies, or other tokens can defeat authentication restrictions and assume other usersí identities.
4 - Cross-Site Scripting (XSS) Flaws - The web application can be used as a mechanism to transport an attack to an end userís browser. A successful attack can disclose the end userís session token, attack the local machine, or spoof content to fool the user.
5 - Buffer Overflows - Web application components in some languages that do not properly validate input can be crashed and, in some cases, used to take control of a process. These components can include CGI, libraries, drivers, and web application server components.
6 - Command Injection Flaws - Web applications pass parameters when they access external systems or the local operating system. If an attacker can embed malicious commands in these parameters, the external system may execute those commands on behalf of the web application.
7 - Error Handling Problems - Error conditions that occur during normal operation are not handled properly. If an attacker can cause errors to occur that the web application does not handle, they can gain detailed system information, deny service, cause security mechanisms to fail, or crash the server.
8 - Insecure Use of Cryptography - Web applications frequently use cryptographic functions to protect information and credentials. These functions and the code to integrate them have proven difficult to code properly, frequently resulting in weak protection.
9 - Remote Administration Flaws - Many web applications allow administrators to access the site using a web interface. If these administrative functions are not very carefully protected, an attacker can gain full access to all aspects of a site.
10 - Web and Application Server Misconfiguration - Having a strong server configuration standard is critical to a secure web application. These servers have many configuration options that affect security and are not secure out of the box