Salaam,
We are having one web application with following configuration:
-Core Java/Servlet/Jsp based
-JRun App server
Login mechanism is added in this application.
It seems that we could face , session fixation attack(Def: The attacker fixes the user’s session ID before the user even logs into the target server, thereby eliminating the need to obtain the user’s session ID afterwards.) due to lack of session management
We are not sure about this. But for precaution, we would like to protect the application.
Also, after investigation, we found that JRun is adding one parameter in Cookie:JSESSIONID=....
Will the problem could be because of that?
OR
Do we need to take some actions for preventing such attacks on our application ?
Thank you....
----------------
Regrds
Baseet Ahmed
----------------
We are having one web application with following configuration:
-Core Java/Servlet/Jsp based
-JRun App server
Login mechanism is added in this application.
It seems that we could face , session fixation attack(Def: The attacker fixes the user’s session ID before the user even logs into the target server, thereby eliminating the need to obtain the user’s session ID afterwards.) due to lack of session management
We are not sure about this. But for precaution, we would like to protect the application.
Also, after investigation, we found that JRun is adding one parameter in Cookie:JSESSIONID=....
Will the problem could be because of that?
OR
Do we need to take some actions for preventing such attacks on our application ?
Thank you....
----------------
Regrds
Baseet Ahmed
----------------