Just happened to me on Businessinsider.
Twitter Tweet Button URL randomly resolves to a .torrent file
41–47 of 47 posts
Re: Twitter Tweet Button URL randomly resolves to a .torrent file
#42My guess: many CDNs allow you to exclude the querystring from the cache key, so it's possible that one person requested the URL with ?torrent in the querystring (which causes S3 to serve a .torrent response) and that the request hit a cold cache. The response with type application/x-bittorrent was then cached under the querystring-less cache key, causing it to be served to anyone else hitting that edge node with the…
Re: Twitter Tweet Button URL randomly resolves to a .torrent file
#43Earlier quoted context omitted.
Relevent FAQ from Amazon S3 FAQ page : http://aws.amazon.com/s3/faqs/#What_is_the_BitTorrent_TM_pro...
Wow, that's amazing. I had no idea Amazon offered that. I also have no idea when I'll ever use it, but still. Damn cool.
Re: Twitter Tweet Button URL randomly resolves to a .torrent file
#44Just got this visiting this article page on TechCrunch => http://techcrunch.com/2013/09/23/facetime-audio-is-apples-bi... Chrome automatically downloaded it => http://cl.ly/image/2u3R2m3j3j1E
Re: Twitter Tweet Button URL randomly resolves to a .torrent file
#45Earlier quoted context omitted.
I don't understand, if the user is prompted to download the file using an external application it's no different than a direct download. If users have their browsers configured to automatically start the download of any .torrent files without confirmation, twitter giving bogus .torrent is no more dangerous than $malware_site linking a .torrent. So that's not a security issue on twitter's site. And anyway, I still fai…
The flow of a (possible) attack is something like this: 1. User configures browser to automatically start torrent downloads when a ".torrent" link is clicked 2. User clicks twitt button which leads to a torrent file 3. The file is downloaded and opened in a torrent client At this point, one could imagine a specifically crafted torrent file which exploits some vulnerability of the torrent client to gain (say) arbitrar…
Re: Twitter Tweet Button URL randomly resolves to a .torrent file
#46Earlier quoted context omitted.
The flow of a (possible) attack is something like this: 1. User configures browser to automatically start torrent downloads when a ".torrent" link is clicked 2. User clicks twitt button which leads to a torrent file 3. The file is downloaded and opened in a torrent client At this point, one could imagine a specifically crafted torrent file which exploits some vulnerability of the torrent client to gain (say) arbitrar…
One could also imagine a specially crafted image file which exploits some vulnerability of the graphics library to gain arbitrary code execution. Then you just need the user to look at the twitter button.