The SpoofedMe social login exploit is a known weakness of the OAuth2 “spec”. The OAuth2 spec doesn’t define strict implementation standards, so developers have free reign to come up with some pretty wild implementations, or hack together a few libraries until it works. And that’s where the problem lies. There is no standard. Furthermore, social login is something that is normally built on top of OAuth2, and there’s no standard for that either. Some folks are trying to standardize social login with OpenID Connect (I like to think of this as “OAuth2-Strict”), but until then we will be facing issues like SpoofedMe because developers are not gods.
The SpoofedMe exploit is actually similar to this one, from a Google security advisory earlier this year:
“An attacker could forge an OpenID request that doesn’t ask for the user’s email address, and then insert an unsigned email address into the IDPs response. If the attacker relays this response to a website that doesn’t notice that this attribute is unsigned, the website may be tricked into logging the attacker in to any local account.” –Link
Thankfully, I read the spec and decided not to implement this gaping security hole in WP-OAuth to begin with. Properly identifying users to perform the account match was one of the biggest design challenges that I encountered because not only were there numerous docs and specs to work through, there were a lot of existing implementations that did it wrong. I had to start from scratch.
On July 9th, 2012 the FBI will shut down a group of servers operated by a cyber crime ring who they’ve recently dismantled. These rogue criminals have jointly infected over 500,000 computer systems in the United States alone with variants of the “TDSS Alureon” malware. This malware redirects your computer’s internet traffic to servers that are run by those criminals, where they tailor your web browsing experience by injecting their own (risky and sometimes dangerous) search results, advertisements, products and services, hoping you’ll give them your money in one way or another.
UPDATE: From the WordPress team: “This is a problem with api.wordpress.org. We’re working on it and should have it resolved momentarily.”
UPDATE 2: Issue has been fixed! I can now search plugins from the backend.
Woops! It looks like something broke with the core WordPress plugin search feature that is powered by WordPress.org.
One minute I was searching and installing plugins like normal and the next minute I was greeted with a confusing message:
“No plugins match your request.”
I was sure the plugin still exists so I went to WordPress.org to verify and sure enough it was there.
A few other users are actively reporting this problem at the WordPress.org forums. Check there to see what I and others are currently saying about it.
This is breaking news so I’m doing a quick post to help anyone else who might be searching Google for a solution. I’ll post an update once I know of one myself but I think it’s safe to say their search is broken for now!
Over the past three days, millions of Blackberry users have been unable to send/receive email and surf the web. Now it’s a global problem with every major news channel and radio station touting the severity.
RIM has posted an official response which is being updated regularly, summing up the problem to an oversight with their email backup system.
Businesses who host their own Blackberry services using Blackberry Enterprise Server (BES) usually get by unscathed, since global outages like this rarely affect the synchronization infrastructure between a Blackberry employee and the company’s BES server.
However, today I can confirm that our BES system is being affected by this outage.