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
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-3154
PUBLISHED: 2020-01-27
CRLF injection vulnerability in Zend\Mail (Zend_Mail) in Zend Framework before 1.12.12, 2.x before 2.3.8, and 2.4.x before 2.4.1 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the header of an email.
CVE-2019-17190
PUBLISHED: 2020-01-27
A Local Privilege Escalation issue was discovered in Avast Secure Browser 76.0.1659.101. The vulnerability is due to an insecure ACL set by the AvastBrowserUpdate.exe (which is running as NT AUTHORITY\SYSTEM) when AvastSecureBrowser.exe checks for new updates. When the update check is triggered, the...
CVE-2014-8161
PUBLISHED: 2020-01-27
PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to obtain sensitive column values by triggering constraint violation and then reading the error message.
CVE-2014-9481
PUBLISHED: 2020-01-27
The Scribunto extension for MediaWiki allows remote attackers to obtain the rollback token and possibly other sensitive information via a crafted module, related to unstripping special page HTML.
CVE-2015-0241
PUBLISHED: 2020-01-27
The to_char function in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to cause a denial of service (crash) or possibly execute arbitrary code via a (1) large number of digits when processing a numeric ...