Timeline for What servers or clients are immune to related-domain cookie attacks? (*.example.com)
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 30, 2012 at 13:46 | comment | added | curiousguy | "because what you get in that case (duplicate cookies, or one cookie masking the other) varies across browsers" this suggest putting a nounce in the cookie key; it doesn't directly help for related domain cookie injection, but at least injected cookies will not hide our owns; we still have to find which cookie is the good one (the cookie key and value will not give this information) | |
| Jun 28, 2012 at 12:39 | comment | added | curiousguy | "The only way to know for sure is to try to delete it and see if it's gone." Could an active attacker constantly recreate it? | |
| Jun 28, 2012 at 11:33 | comment | added | bobince | @curiousguy: unfortunately not reliably, because what you get in that case (duplicate cookies, or one cookie masking the other) varies across browsers. The only way to know for sure is to try to delete it and see if it's gone. | |
| Jun 27, 2012 at 23:30 | comment | added | curiousguy | "attempt to guess at what level the cookie was set," what if I guess the cookie is at some level (example.com), and I add a cookie at another level (foo.example.com), would that be a way to verify my guess? | |
| Mar 14, 2012 at 0:00 | vote | accept | makerofthings7 | ||
| Mar 7, 2012 at 10:04 | history | answered | bobince | CC BY-SA 3.0 |