30,044 reputation
336107
bio website bishopfox.com
location
age
visits member for 3 years, 10 months
seen 1 hour ago

Test everything, trust no one.

Do not trust any security related answers you see on StackOverflow.com (SO) / Security.StackExchange.com (SE). Not from me, not from anyone. There are very smart people on SO/SE and there are excellent answers given, although the right answer is not always chosen.

I have been writing exploit code for a while. There is no perfect system, vulnerable code will always exist.


Oct
31
revised Is there a secure way to share sessions in the same server with different sub domains?
deleted 1 character in body
Oct
30
revised Is there a secure way to share sessions in the same server with different sub domains?
added 45 characters in body
Oct
30
revised Is there a secure way to share sessions in the same server with different sub domains?
added 117 characters in body
Oct
30
revised Is there a secure way to share sessions in the same server with different sub domains?
added 507 characters in body
Oct
30
reviewed Approve suggested edit on Is there a secure way to share sessions in the same server with different sub domains?
Oct
30
answered Is there a secure way to share sessions in the same server with different sub domains?
Oct
29
comment CSRF Token Strategy
@gr8dane If a developer doesn't have a good understanding of the SOP, they will write hazardous software. There is no shortcut here, if you don't like the Google browser security handbook, look up Wikipedia, or a Mozilla reference.
Oct
29
revised CSRF Token Strategy
added 55 characters in body
Oct
29
comment What is same site scripting and what are some exploit scenarios?
Your title is almost longer than your question, and they are both different questions. wtf mate?
Oct
29
comment Rooted android cached password
If you have root can do whatever the hell you want.
Oct
29
revised CSRF Token Strategy
added 12 characters in body
Oct
29
revised CSRF Token Strategy
added 44 characters in body
Oct
29
comment CSRF Token Strategy
@gr8dane Perhaps you should be asking the question: "How can the same-origin policy protect my web application?"
Oct
29
comment CSRF Token Strategy
No csrf exploit?
Oct
29
revised CSRF Token Strategy
deleted 22 characters in body
Oct
29
comment CSRF Token Strategy
@gr8dane the SOP holds the fundamental answer to your question. Also, your example form is the definition of IDOR, that can't be ignored. You can't pass a user ID as a $_GET, it must be apart of the $_SESSION. The CSRF token is a $_SESSION variable, that is compared to a $_GET or $_POST variable, which creates a CSRF-synchronization token. This is a secret that the attacker cannot know, because of the SOP.
Oct
28
awarded  Enlightened
Oct
28
awarded  Nice Answer
Oct
28
revised CSRF Token Strategy
added 256 characters in body
Oct
28
answered CSRF Token Strategy