3 ms·
I mentioned this the other day in a comment, but I figured it gets a lot more visceral punch if you actually see it happen, so I wrote up the consequences in an
by patio11 16y ago
I mentioned this the other day in a comment, but I figured it gets a lot more visceral punch if you actually see it happen, so I wrote up the consequences in an article and wired together a working tech demo. I haven't seen anybody exploit this misfeature "in the wild" yet, but then again I'm not exactly plugged into the social networking scene.
It astounds me that somebody thought making the Like button be silent opt-in to "permission" marketing was a good idea.
Added bonus points (not covered in article): this creates a security hole in every Liker's account, because it slaves the security of their News Feed to the security of every site they have ever liked. Pretend you like something published by Scrappy Startup A. Six months pass. Scrappy Startup goes out of business and their URL gets grabbed, or Scrappy startup gets their server owned, or Scrappy Startup merely permits defacement of the contents of their HEAD. This lets the attacker immediately assert publishing privileges for all connections created by Likes (6+ months ago), and then spam the connected Facebook News feeds with live URLs carrying an endorsement from Scrappy Startup.
Now pretend Scrappy Startup is, or purported to be, Obama. (Thumbnail sketch: you and 10,000 other people favorite a picture of Obama hugging two puppies titled "Obama Gives Constituents a Lift", six months later the Facebook login crowd sees "Obama Gives Constituents a Lift: Click here and put in your bank account details to receive your instant stimulus package".)
- Sukotto 16y agoI'm a bit surprised that you published this to your bingo blog and not Kalzumeus.com. Aren't you worried about your stereotypical user clicking it by accident?
- patio11 16y agoThe only way in is via direct link to that URL. I put it there because I happened to have Rails code written to do most of the work here (back from when I implemented Like buttons for the site, prior to understanding what they actually do), and because I'm positive Nginx can take the load (it is 100% static content after the first access) but less than sanguine about my Apache setup.
- mikeknoop 16y agoYour "takeover" scenario isn't true and cannot happen simply by having a URL change ownership. You need access to both the domain AND the Facebook user account or application to which the open graph objects (websites) are tied to. Also, if you can get access to a Facebook user account or application, you don't even need the domain name.
- patio11 16y agoI'm pretty sure, but not positive, that I did it to myself earlier today: edit the page, add in a new og:app_id pointing to an application that you control. The documentation mentions the object's title and type being durable, and I wasn't able to successfully overwrite those, but you can change the other parameters and then just call the Lint tool on the page again. (n.b.: If you have something as og:type="article", that apparently causes there to be no OpenGraph node created for the page in spite of what the docs say. That might be a bug. Anyhow, the upshot is that this means that everything tagged as an "article" is safe.) But I think I remember being able to add an app to my "cause" after it was first liked.
- natrius 16y agoIt is indeed a bug: http://bugs.developers.facebook.net/show_bug.cgi?id=10448 http://bugs.developers.facebook.net/show_bug.cgi?id=10448
- edanm 16y agoIs there some kind of limit to the number of postings an application can make on your wall? I.e. "x posts per hour"?