Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think some confusion is still in our web-security knowledge world. You are afraid of <strong>Cross Site Request Forgery</strong>, and yet describing and looking for solution to <strong>Cross Site Scripting</strong>. </p> <p><strong>Cross Site Scripting</strong> is a vulnerability that allows malicious person to inject some unwanted content into your site. It may be some text, but it also may be some JS code or VB or Java Applet (I mentioned applets because they can be used to circumvent protection provided by the <code>httpOnly</code> flag). And thus if your aware user clicks on the malicious link he may get his data stolen. It depends on amount of sensitive data presented to the user. Clicking on a link is not only attack vector for XSS attack, If you present to users unfiltered contents provided by other users, someone may also inject some evil code and do some damage. He does not need to steal someone's cookie to get what he wants. And it has notnig to do with visiting other site while still being logged to your app. I recommend:<a href="https://www.owasp.org/index.php/XSS_%28Cross_Site_Scripting%29_Prevention_Cheat_Sheet" rel="nofollow">XSS</a> </p> <p><strong>Cross Site Request Forgery</strong> is a vulnerability that allows someone to construct specially crafted form and present it to Logged in user, user after submitting this form may execute operation in your app that he didin't intended. Operation may be transfer, password change, or user add. And this is the threat you are worried about, if user holds session with your app and visits site with such form which gets auto-submited with JS such request gets authenticated, and operation executed. And httpOnly will not protect from it because attacker does not need to access sessionId stored in cookies. I recommend: <a href="https://www.owasp.org/index.php/CSRF" rel="nofollow">CSRF</a></p>
    singulars
    1. This table or related slice is empty.
    1. POHow do I protect sensitive information from cross site access?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USdamiankolasa
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COYou are right in that my question is not related to XSS. Note that I said my script was included on the attacker's site, not the other way around. My question is somewhat related to CSRF, but it is not quite the same. CSRF is about a third party site performing a sensitive action on behalf of the user. My question is about a third party site reading sensitive information on behalf of the user. For example, to prevent CSRF, I have to check a CSRF-token. But how do I prevent the attacker from reading the CSRF-token in the first place?
      singulars
      1. PO
      1. USJesper Kristensen
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload