security - Javascript hijacking, when and how much should I worry? -


ok, i'm developing web app has begun more ajaxified. read blog talked javascript hijacking, , i'm little confused when it's problem. want clarification

question 1: problem/vulnerability?

if site returns json data 'get' request has sensitive information information can wrong hands.

i use asp.net mvc , method returns json requires explicitly allow json requests. i'm guessing trying save uninitiated security vulnerability.

question 2: hijacking occur sniffing/reading response it's being sent through internet? ssl mitigate attack?

question 3: led me ask question myself. if i'm storing page state in local javascript object(s) of page, can hijack data(other logged in user)?

question 4: can safely mitigate against this vulnerability returning json 'post' request?

the post linked talking csrf & xss (see comment on question), in context:

is problem/vulnerabiliy ("if site returns json data 'get' request has sensitive information information can wrong hands.")?

no.

does hijacking occur sniffing/reading response it's being sent through internet?

no.

if i'm storing page state in local javascript object(s) of page, can hijack data(other logged in user)?

it depends. depends on whether you're storing data in cookies , haven't set right domain, or path. depends on whether there's security vulnerability on client browser allow script gain access data typically restricted. there numerous other vectors of attack, , new ones discovered time. long , short of is: don't trust browser any confidential or secure data.

can safely mitigate against this vulnerability returning json 'post' request?

no (it's not single vulnerability, it's set of classes of vulnerabilities).


Comments

Popular posts from this blog

linux - Using a Cron Job to check if my mod_wsgi / apache server is running and restart -

actionscript 3 - TweenLite does not work with object -

jQuery Ajax Render Fragments OR Whole Page -