Daemonite: Top Vulnerabilities in Web Applications Archive

Daemonite: Top Vulnerabilities in Web Applications Archive


Wednesday, January 22, 2003
Top Vulnerabilities in Web Applications

Open Web Application Security Project released a great summary of typical web application vulnerabilities. For many this "top ten" will be stating the obvious, but nevertheless it is a great check list for dev teams to sign off on prior to going live.

The Open Web Application Security Project (OWASP) is dedicated to helping organizations understand and improve the security of their web applications and web services. This "top ten" was created to focus government and industry on the most serious of these vulnerabilities.

Top Vulnerabilities in Web Applications

A1

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.

A2

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.

A3

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.

A4

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.

A5

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.

A6

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.

A7

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.

A8

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.

A9

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.

A10

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.

The full report (available as a PDF 366kb) explains why each issue is dangerous, how to test if you're at risk, and recommended best practice to protect your application. It's well worth the download if any of the following issues spark an interest.

Posted by modius at 12:31 AM | Permalink
Trackback: http://blog.daemon.com.au/cgi-bin/dmblog/mt-tb.cgi/67

Comments

The PDF is on the front page of the OWASP site listed above!

Posted by: Geoff Bowers on February 3, 2003 12:26 AM