Note that there are some explanatory texts on larger screens.

plurals
  1. USKim L
    primarykey
    data
    text
    plurals
    1. COHibernate lazy loading exceptions are common with Vaadin if you don't handle them correctly. Usually, you will use a session-per-request pattern, which means that your entities will be deattached from the hbn session at the end of the http request. If you try to lazy load anything outside the same http request, a lazy loading exception will be thrown - unless you re-attach the entity to the active session.
      singulars
    2. CO@The Rook, like I said, I misread your response and my comment was about multi-paged forms. The iframe only helps when attacking multi-paged forms, it had nothing to do with the referer header. Here's an example of how an application can be tricked into thinking the referrer is something else than what it actually is. This attack doesn't actually spoof the referer header, but rather demonstrates that everything isn't exactly what you think it is. Make sure you read other blog posted linked to in the beginning. http://blog.quaji.com/2009/08/facebook-csrf-attack-full-disclosure.html
      singulars
    3. CO@The Rook, sorry, re-read your post and what you described will work as it is basically the same I described in my reply, just another strategy for creating the secret token. I first read that your post was about a multi-paged form, which I described an attack for (it will work if the pages are predictable and thus there is no need to read the HTTP response). My attack is valid and doesn't conflict with the same origin policy, as it never requires to read the response. In other words, my bad. If you still think my attack is not valid, I can provide you with a proof-of-concept :)
      singulars
 

Querying!

 
Guidance

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