225 reputation
311
bio website
location
age
visits member for 3 years, 2 months
seen Apr 11 at 10:21

Mar
14
awarded  Notable Question
Feb
12
awarded  Notable Question
Oct
28
awarded  Popular Question
May
31
awarded  Popular Question
May
14
awarded  Popular Question
Apr
22
comment Tampering req.getParameter() Vs req.getAttribute()
@asudhak request.getAttribute and request.getParameter do different things .. code above is reading attribute and not the parameter.
Apr
5
comment Extract cookies from pcap
ngrep.sourceforge.net/usage.html haven't used it myself but looks it will do what you looking for
Apr
5
comment Is Request.getHeader(“host”) vulnerable?
Host header can result in stored XSS and not in reflective XSS (unless you are trying to XSS yourself). Server processing your request doesn't need to have the same hostname as the host you sent your request to. So you can a request to host a with host header set to host b. But in most scenarios you will only be affecting yourself and not anyone else unless developer have made a mess in the code and there is some persistence of host header which will somehow be used for some other users.
Apr
5
comment Tampering req.getParameter() Vs req.getAttribute()
-1 Value from request.getAttribute can not be directly tempered by request data unless the developer sets any data from request directly to the named attribute being used for redirect URL.
Sep
11
awarded  Yearling
Jun
22
comment Securing an API for mobile access
You already got many detailed answer..so I am not going to write another one.. simple solution- Ask mobile based users to authenticate once using a username password.. generate a authentication token at server ( keep a copy with you associated with username).. store the token on mobile and use this token in further communications... you can make the token for always or limited time based on your requirements... there are still risks around lost device etc but still better than embedding credentials in code... Disclaimer : This is not most secure solution just better than current situation
May
18
comment Does vulnerability exist when using XHR with GET method and custom anti-CSRF HTTP header?
@AndreyBotalov even if it doesn't appear in URL it will be logged by web server and proxy server ... along with all your params. And issues 3 : whatever you send to client is wide exposed one way or other... view source , check javascript, intercept own request there are numerous ways. You really need to get your fundamentals right before calling the issues irrelevant ...
May
17
answered Does vulnerability exist when using XHR with GET method and custom anti-CSRF HTTP header?
May
9
comment Session fixation attack
This is applicable in scenarios where attacker has limited access to the system. In real life scenarios, this attack works well.
May
8
answered Session fixation attack
May
1
asked Set Cookie in XHR response : How different browsers handle this?
Apr
24
comment When form submission fails, password field gets blanked, why is that the case?
You never send back the password. Google around about caching
Apr
17
comment XSS : Content-type: application/json
I have the same thoughts. Lets wait if someone wants to counter this, otherwise I will mark this as the right answer
Apr
16
comment XSS : Content-type: application/json
Good points. (Un)Fortunately application is not writing the response to body or to any DOM element. User input is coming back in case of error message so the call back method just doesn't do anything with it .
Apr
16
comment XSS : Content-type: application/json
If you could also put reason for vote down in comments, that would really help in improving my questions in future. Thanks