Skip to main content

Protection and Response to User Account Leaks

Today it is being widely published that Gawker media has had their entire databased of user accounts and passwords (DES encrypted) leaked to the public.  Although this event may have been limited to those with user accounts on Gawker properties, imagine this happening on a major service like google, hotmail, or your bank.

The two most significant impacts to most people are:

1)  Gaining access to the Gawker services exposed.  Once the encryption is brute forced on the password data it is possible for someone to directly login to the service as you.

2)  Reuse of passwords on other services.  Because humans are creatures of habit, we tend to reuse usernames and passwords across services, so if someone can find your email address and password, they can attempt to login to other services as you as well.

This provides an opportunity to reflect on methods of preventing and responding to these types of events.

Response - Although it appears to be a good idea to change the password on the affect service account immediately, one of the serious issues with this is that the systems on which you are changing the password may be compromised which would lead to the attacker knowing the new password.

Also, if you are the security manager for an organization, get a copy of the dumped account information and find out if you have any affected users.  Do a search for your company name / domain name, and/or search for hashes of email addresses.

Prevention - IMPORTANT - stop using the same passwords across systems.  Although this is an inconvenience, using different passwords across services will prevent someone from using a compromised password on other services.  Come up with a scheme that works for you to create unique passwords for different services that you can remember.

Use strong passwords.  There are great strong password generators that you can use to come up with good passwords.

Change your passwords occasionally.  Once a year will prevent really stale passwords from being compromised and used, plus it will keep you exercising your brain to remember new passwords.

Use multifactor authentication where possible.  Google and others have made it easy to implement two factor authentication using things like smart phones, SMS, public phones, etc.  These are easy to implement and makes a password compromise a non-event.


Popular posts from this blog

Local Classified Penny Auction Scam

While there are a lot of new posts regarding the new ways to exploit people using novel techniques and 0day exploits, there continues to be a rash of tried and true methods of coercion.  I want to just walk through a simple example and reflect on how effective these methods continue to be. Many people turn toward online classified sites to buy and sell items online.  This example starts with which even I've used on occasion to find used electronics and other items.  Doing a search on the site for a " Samsung Galaxy Note 2 " returns a posting from today with someone selling one for an unreasonably priced unit. $125 for a $500 phone?, but what if it's for real?  No harm in just asking some simple questions.  Email sent with some obvious questions regarding the condition and location. About an hour passes before I get a response from what appears to be a legit seller. Notice no answer to the questions I asked, but a friendly pointer at where th

Edmonton HeartBleed Information Session - April 16th, Royal Glenora Club

Since the latest major OpenSSL vulnerability was publicly disclosed, many people and organizations are scrambling to understand, respond and prepare themselves for the future.  Twitter, vendor support channels and media outlets have been quick to cover different angles of the issue but there has been overwhelming amount  of information released. With all this information, it can be difficult to understand what's relevant.  To help clarify we holding a special ISACA sponsored 2-hour session on Wednesday, April 16th, starting at 12:00pm at the Royal Glenora Club.   Benoit and I will be attempting to explain as much of the issue as we can from a technical and non-technical perspective, discussing the vulnerability, its scope with relation to our personal and professional lives and other related concerns such as our trust in the public PKI system.  The second hour we will be an interactive discussion about how others are dealing with problem, questions about related topics,

Touch ID - Distributed Fingerprint Lookup

All the press regarding the new Touch ID fingerprint biometric on Apple's new iPhone has brought some insight into how to misuse this service.  Most of the critics have focused on circumventing the device to gain access or Apple deciding to share the data with the Government. One interesting perspective that I haven't seen covered yet is if the system could be used as a distributed matching system for existing fingerprint image systems.  In an over simplified view of the process, a law enforcement agency can take an acquired fingerprint and search for patterns in the database of collected prints and spit out possible matches. Although Apple states that an API won't be available for apps, it is conceivable that such an interface might exist, and provide the ability to take an acquired print (either from the iPhone hardware or from software) and check it for validity against the stored print. There are some limits to this, as there is likely only going to be one prin