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-http://software-security.sans.org
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:

<security-constraint>

<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>

</security-constraint>

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:

<session-config>
<cookie-config>
<http-only>true</http-only>
</cookie-config>
</session-config>

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:

<session-config>
<session-timeout>10</session-timeout>
</session-config>

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:

<session-config>
<tracking-mode>COOKIE</tracking-mode>
</session-config>

Comments

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.
February 6, 2011 at 1:42 AM
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
February 15, 2011 at 5:05 PM
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 needs...at 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.
February 16, 2011 at 5:25 PM
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
March 9, 2012 at 5:21 AM
Nilesh Kumar said…
@Anonymous: Yes..correct!
March 9, 2012 at 5:05 PM
Post a Comment

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. T...
1 comment
Read more

'Information Leakage-Improper Error Handling' dropped

From Owasp Top 10 2010 List, the issue 'Information Leakage-Improper Error Handling' has been dropped. But it's not the final list,its child release actually. Bu I feel it shouldn't be set aside because its still the one of the prevalent issues these days. That's why I mailed to Dave Wicher: Hi Dave, Excellent work, Congrats! Just one little query- Don't you think that Information Leakage & Improper Error Handling still deserves to be in Top 10? Dave replied: This topic is clearly a very prevalent issue that deserves attention by most organizations. However, the typical impact of such a flaw is usually very low. Therefore, the overall risk of this type of flaw is lower than the other items in the top 10, which is why it was replaced in this update with one of the 2 new items. Regarding dropping Info Leak/Error handling - It is incredibly prevalent, no question. But their impact is typically very low, so the overall risk is low, which is why it fell out of t...
3 comments
Read more

jtool - an alternative to otool

jtool comes with a capability of running on Linux environment. Some ipa scanning tools are created to run on Linux environment where mac environment is not available. In such cases tools such as otool and class-dump-z will not work. So jtool can be an alternative to otool. For more information on jtool please refer to http://www.newosxbook.com/tools/jtool.html . It lists down various commands which have same output as otool or a equivalent. There are several commands mentioned in link. But for our customized requirements and basis checks I have listed down the below ones after running on many binaries. The outputs are similar or equivalent to otool and class-dump-z: Commands for checking PIE flag (ASLR) in jTool jtool -d -v -arch | grep stack ·           Automatic Reference Counting (ARC) protection: jtool -d -v -arch | grep _objc_release ·           To check if the devic...
1 comment
Read more