Skip to main content

Few common web.xml misconfigurations-Part I

While doing code review usually I find various misconfigurations. I am trying to compile them here.
Although they might not be a comprehensive list and something I may miss, but will touch most of the common points: Refer-http://software-security.sans.org

1. Authentication & Authorization Bypass:

<security-constraint>
<web-resource-collection>
<web-resource-name>secure</web-resource-name>
<url-pattern>/secure/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name>admin</role-name>
</auth-constraint>
</security-constraint>

The above configuration shows how to setup web-based control. Here the assumption is that the everything in 'secure' directory must be accessible by 'admin' user only by using methods listed in tags i.e, GET and POST. No other methods should be allowed. But that is not the case!
In fact any HTTP method which is not explicitly enlisted here (HEAD,or any junk values like, JEFF,TEST etc) can be used to access the resources under 'secure' directory. It's also called HTTP verb tampering. Arshan Dabirsiaghi has a nice paper that summarizes this issue.
The solutions is just simply remove all above elements from above code and configuration will be properly applied to all requests.

2. Absence of Secure Flag: Sometimes some websites revert back to non-SSL connection or can be accessed over non-SSL connections (http://). This leaves the sessionID vulnerable to capturing which may lead to session hijacking. The sessionID must be marked with 'secure' flag.
In order to do that the following configuration can be defined in web.xml:

<session-config>
<cookie-config>
<secure>true</secure>
</cookie-config>
</session-config>


3. Customized Error pages are not defined: Sometimes the application faces unexpected error and is not able to handle it properly following which it displays it directly to the end user in form of stack traces or other signs. This may be a useful information for an adversary to launch attacks as it may reveal sensitive information about the code/platform/technology of the application and also tell about the application's input validation strategies. The developer should avoid these errors to be leaked to the end user. They should define some custom pages in the web.xml so that in case of error the applications should present a generic and customized page to the user instead of specific information-no matter what error occurs.
The following setting can be used:
Using the following configuration a nice error page will be displayed whenever the application responds with an HTTP 500 error. You can add additional entries for other HTTP status codes as well.

<error-page>
<error-code>500</error-code>
<location>/path/to/error.jsp</location>
</error-page>

Comments

Great information.Great thoughts.It is very important to know all the people.It is great and happy to read this blogs.Thanks for making it.
Anonymous said…
Here is the original article published in Aug 2010. Plagiarism? Decide for yourself:

http://software-security.sans.org/blog/2010/08/11/security-misconfigurations-java-webxml-files

Popular posts from this blog

Using an AirPcap device in Windows with Wireshark

Capturing wireless traffic in a Windows environment is unfortunately not as easy as a setting change. As with most Windows-based software, drivers in Windows are often not open source and do not allow for configuration change into monitor mode. With this in mind, we must use a specialized piece of hardware known as an AirPcap device. Once you have obtained an AirPcap device you will be required to install the software on the accompanying CD to your analysis computer. The configurable options include: • Interface - Select the device you are using for your capture here. Some advanced analysis scenarios may require you to use more than one AirPcap device to sniff simultaneously on multiple channels. • Blink LED - Clicking this button will make the LED lights on the AirPcap device blink. This is primarily used to identify the specific adapter you are using if you are using multiple AirPcap devices. • Channel - In this field, you select the channel you want AirPcap to listen on. Extension C...

Some one watching where you visited!

Yes... Mozilla has been susceptible to browser-history stealing java script code. Today, Giorgio posted some cool information about the exploit. Mozilla is already working on this. This bug has been reported. Actually they have set up a web site to show the proof-of-concept. Visit www.statrpanic.com in FF,Safari or Netscape and it will tell you which websites have you been already ! But I am not sure it will work in IE or not because my IE is not responding to the website. Clearing history of visited website makes you safe to this attack. I mean this is one way..may be there are other ways to exploit this. But I have found this effective. Try it yourself in FF and then in IE and see the results.

Hijacking SSL

SSL has been in centerstage of researches as well as attacks for quite long time. Last year in a conference in Germany researchers showed how to generate duplicate certificates exploiting MD5 hashing to break SSL. Later in Black Hat, Maxie showed how to exploit a field in SSL certificates to sign an own forged certificate to present it to the client. The main feature of this attack was that the client will never get any warning dialog box by the browser and subsequently the hacker doing an MITM can see the conversation between the client and server. The client will even get a PADLOCK sign to be assured that all things are going via encryption, but in reality it's not. Maxie released a tool SSLStrip to carry out these attacks. The tool has been used by many researchers around the world to carry out the attacks. They all used Unix machines as many open source utilities makes it easier to run the tool on it. My attempt was to run the tool on a Windows machine. It has been never easy t...