3 added 25 characters in body
source | link

Once upon a time flash was vulnerable to CRLF injection (IE was also vulnerable), and this could have been used to set the Cookie: HTTP request header to exploit cookie-based XSS. But this is no longer the case. It is not possible to set a Cookie on another domain. If you could set cookies for other domains it would make session fixation very difficult to prevent (if not impossible).

Once upon a time flash was vulnerable to CRLF injection, and this could have been used to set the Cookie: HTTP request header to exploit cookie-based XSS. But this is no longer the case. It is not possible to set a Cookie on another domain. If you could set cookies for other domains it would make session fixation very difficult to prevent (if not impossible).

Once upon a time flash was vulnerable to CRLF injection (IE was also vulnerable), and this could have been used to set the Cookie: HTTP request header to exploit cookie-based XSS. But this is no longer the case. It is not possible to set a Cookie on another domain. If you could set cookies for other domains it would make session fixation very difficult to prevent (if not impossible).

2 added 7 characters in body
source | link

onceOnce upon a time flash was vulnerable to CRLF injection, and this could have been used to set the cookie: http reaquestCookie: HTTP request header to exploit this issuecookie-based XSS. But this is no longer the case. It is not possible to set a Cookie on another domain. If you could set cookies for other domains it would make session fixation very difficult to prevent (if not impossible).

once upon a time flash was vulnerable to CRLF injection, and this could have been used to set the cookie: http reaquest header to exploit this issue. But this is no longer the case. It is not possible to set a Cookie on another domain. If you could set cookies for other domains it would make session fixation very difficult to prevent (if not impossible).

Once upon a time flash was vulnerable to CRLF injection, and this could have been used to set the Cookie: HTTP request header to exploit cookie-based XSS. But this is no longer the case. It is not possible to set a Cookie on another domain. If you could set cookies for other domains it would make session fixation very difficult to prevent (if not impossible).

1
source | link

once upon a time flash was vulnerable to CRLF injection, and this could have been used to set the cookie: http reaquest header to exploit this issue. But this is no longer the case. It is not possible to set a Cookie on another domain. If you could set cookies for other domains it would make session fixation very difficult to prevent (if not impossible).