The scope of this vulnerability is quite low, as you need access to the device you know user will login later. So, twitter has decided it to be a "won't fix". Anyways it would be a fun exploit and would serve as a good example to understand CSRF attack as you can try it out.
The CSRF token issued by twitter doesn't change unless you restart your PC.
 |
| CSRF token after login |
 |
| CSRF token before login |
Details of the attacks scenario in a shared workstation environment
The attacker simply copies the authenticity token.It is a hidden field with the id "authenticity_token". This token is the only protection against the CSRF attack.
Forge an html document and place the copied authenticity token in the request.
Wait for the victim to login and send the link. With what you want to be tweeted in the value of the field with name status.
When the vicitm clicks on the link, a tweet will be posted from his account.
" || calc ||
ReplyDelete