Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

12/13/2010
08:48 PM
Adrian Lane
Adrian Lane
Commentary
50%
50%

Gawker Goof

Sometimes it helps knowing what not to do with database security to clarify why you need database security -- and sometimes somebody else goofs up real bad and sheds light on the little security details you need to get right

Oracle came out with Database Security Worst Practices this week, a list of seven things you should not do. It's a fairly good list if you are an Oracle customer, covering the basic preventative security settings you should check before any database server is deployed into production. But I have a couple that trumps them all, especially if your databases support Web applications:

Don't store passwords in clear text!

Don't encrypt passwords if you leave the encryption keys unsecured!

Apparently that is just what the developers at Gawker did. If you have a user account on Gawker, Gizmodo, Jalopnik, Jezebel, Kotaku, Lifehacker, Deadspin, io9, or Fleshbot, Gawker is telling you that your user credentials have been compromised. For the user credentials to have been compromised means they were stored in clear text, or the sites were using encryption and left the encryption keys somewhere easy to get. As their websites claim, they were encrypted; I'll give them the benefit of the doubt. But it means the hackers have access to everything the users did, and possibly some of the administrative accounts as well.

Most public-facing Web applications do not encrypt passwords. They use what is called a hash function. Both completely alter the original value so it's pretty much impossible to guess the password. The difference between the two is that encryption can be reversed back into the original value by using a secret encryption key. The security of the password is only as strong as the security of the key. A hash function permanently obfuscates the password. This is done so if someone should manage to break into your database, he does not automatically obtain all user passwords; rather he gets the hashed value that cannot be used as a password. When a user logs into the system, the password he sends to the database is also hashed; if the new hashed value matches the hashed value stored for that user account, that person is logged into the database.

I am going to bet a lot of you already knew that. And you know that every major relational database platform stores passwords for users of that database as a hashed value in a secured table. And most RDBMSs offer a hash function as a stored procedure call as well, just in case you maintain your own user and password tables.

But this bears explaining; clearly some developers out there apparently did not get the memo that hackers hack databases. And that secret encryption keys need to be kept secret. If they had or used hashing, then hackers getting the user name -- and even the email credentials -- the accounts would not have been compromised.

This is a colossal failure that would place No. 3 on my list of things not to do with database security. No. 2 would be clear text passwords. No. 1 would be leaving the administrator password at the default setting. Let's hope Gawker at least got that right.

Adrian Lane is an analyst/CTO with Securosis LLC, an independent security consulting practice. Special to Dark Reading.. Adrian Lane is a Security Strategist and brings over 25 years of industry experience to the Securosis team, much of it at the executive level. Adrian specializes in database security, data security, and secure software development. With experience at Ingres, Oracle, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
SOC 2s & Third-Party Assessments: How to Prevent Them from Being Used in a Data Breach Lawsuit
Beth Burgin Waller, Chair, Cybersecurity & Data Privacy Practice , Woods Rogers PLC,  12/5/2019
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Our Endpoint Protection system is a little outdated... 
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-1689
PUBLISHED: 2019-12-10
Mozilla Firefox 20.0a1 and earlier allows remote attackers to cause a denial of service (crash), related to event handling with frames.
CVE-2016-10001
PUBLISHED: 2019-12-10
inets in Erlang possibly 22.1 and earlier follows RFC 3875 section 4.1.18 and therefore does not protect applications from the presence of untrusted client data in the HTTP_PROXY environment variable, which might allow remote attackers to redirect an application's outbound HTTP traffic to an arbitra...
CVE-2019-6183
PUBLISHED: 2019-12-10
A denial of service vulnerability has been reported in Lenovo Energy Management Driver for Windows 10 versions prior to 15.11.29.7 that could cause systems to experience a blue screen error. Lenovo Energy Management is a client utility. Lenovo XClarity Energy Manager is not affected.
CVE-2019-6192
PUBLISHED: 2019-12-10
A potential vulnerability has been reported in Lenovo Power Management Driver versions prior to 1.67.17.48 leading to a buffer overflow which could cause a denial of service.
CVE-2019-4095
PUBLISHED: 2019-12-10
IBM Cloud Pak System 2.3 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM X-Force ID: 158015.