Skip to main content

Few common web.xml misconfigurations-Part II

Well my colleague Sam says, I am slowing down on posts as I had written last one long time back :).
Here's my first in this month, second and concluding part of the last months series.
Few more mis-configurations:Refer-
4. SSL Not Configured:
No need to tell explicitly why SSL is necessary. Its protects the transit communications from sniffing,tampering by encrypting it and also-more important provides authentication. So confidentiality is preserved. Configure it as following:




5. Not marking Cookies as 'HTTPOnly':

Cookies marked with HTTPOnly ensures that the cookies can not be accessed by javascripts in browsers making it more safe against most of the and common Cross-Site Scripting attacks (XSS)-still possible with Cross Site Tracing (XST) attacks though.
Use the following configuration:


6. No Session Time-Out:

As a best pratcice for session management always set time-out for the applications. If the user is idle for some specific amount of time, invalidate the session that will make the application more secure against hijacking:


The application will expire after 10 minutes of inactivity. Don't set any -ve values as it will make the application to not expire indefinitely.

7. Don't use URL parameters to store sessionIDs:

Sessions can be stored in two places mainly: Cookies and URL parameters. The last one is less secure as URLs can be logged/cached in some places like browser history. Make sure than you store sessionIDs in cookies:



Sam said…
Nice job Nilesh. You should start compiling these into a collection that could be called "Nilesh's Greatest Hits" :)

Keep up the good work, and don't pay too much attention to that Sam guy. He's just giving you a hard time.
Anonymous said…
Hi Nilesh,

Can you please clarify that these configuration has to be done at container's level or can be handled at web application level?

Thanks & Regards
Suman Kumar
Nilesh Kumar said…
@Sam: Sure Sam, I shall make a collection of them and gift you on your next India visit :).

@Anonymous: It depends on your container level it should affect all the applications and at app level it will affect the particular web application for which you edit the web.xml file. Hope that helps.
Anonymous said…
Here is the original article published in Aug 2010. Plagiarism? Decide for yourself:
Nilesh Kumar said…
@Anonymous: Yes..correct!

Popular posts from this blog

File Upload through Null Byte Injection

Sometimes, during file upload we come across situation wherein there would be check on the file extension at the client side as well as server side too. If the application does allow only .jpeg extension to be uploaded, the client side java script checks for the extension of the file before passing the request. We all know that how easily this can be defeated.
Some applications, checks for the extension at the server side also. That's not easy to bypass. However there are some ways with which it still can be bypassed. Most of server side scripts are written in high level languages such as Php, Java etc who still use some C/C++ libraries to read the file name and contents. That leads to the problem. In C/C++ a line ends with /00 or which is called Null Byte. So whenever the interpreter sees a null byte at the end of the a string, it stops reading thinking it has reached at the end of the string.
This can be used for the bypass. It works for many servers, specially php servers. Th…

SQL Injection in search field

Earlier I had written about performing SQL injection in search field and how to do a DoS attack and privilege escalation using 'Like' operators. Now another SQLi exploitation I came across recently. That too in the search field. This becomes important as lots of people don't pay much attention on the search forms/ fields in the application. My aim is to show that a search form can also be exploited with SQL Injection. The following queries are based on a real world exploitation. The steps and data are for just illustration purpose only. Suppose, the search form provides the details of users who have accessed the application some time and their login time details etc, we just need to provide their name in the search box provided. All the data were being going as Post request. So, to just fingerprint the database, I provide, 'nil'+'esh' in the search field and it successfully gives me the results. That means the database behind the application is concatenat…

Insecure protocols

Some basic insecure protocols and risk associated with them: