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

7/12/2012
10:11 AM
Adrian Lane
Adrian Lane
Commentary
50%
50%

Let's Ask 'Why?'

Why are big firms still vulnerable to SQL injection?

Database security people as "Why?" a lot. "Why didn't they patch the database?" "Why did they move production data into testing?" "Why are they still vulnerable to SQL Injection?" "Why did forget to change the default admin password" "Why are we seeing these same simple errors?"

There has been a slowdown of blogging on the topic of database security of late. Not just me, though I am equally guilty, but just about every DB security expert I know has not had very little to say on the subject in the past year. Worse, look at the conference agenda's of RSA and Black Hat -- two of the industry's largest security shows -- and you are lucky if there is one presentation on the subject. I think since we have been seeing the same headlines over and over for so long, database security has lost its luster. Mobile, cloud, or even social media security, that's sexy. SQL injection? Not sexy, but it sure is effective.

So this is yet another opportunity to ask the question: "Why?" Have databases become so secure that it's not a topic for discussion? Not likely; it has being reported that Yahoo! suffered a breach today. The cause? SQL injection. Have you heard this before? Yes, you have.

According to data published from Privacyrights.org (CSV), SQL injection was the means used to extract 83 percent of the total records stolen in successful hacking-related data breaches from 2005 to 2011. Blink, and tomorrow it will be yet another big company. We don't see code injection and buffer overflow attacks like we used to -- the vendors have done a much better job at fixing those issues -- but SQL injection, compromised credentials, and poorly configured systems are still prevalent. These are the same basic threats we've seen for the past decade, and we see the same breach headlines!

We don't ask the question, "Why attack the database?" because we know the answer: That's where the data is. Databases are still a principle target, and most of the principle threat vectors remain viable for an attacker.

Database security programs, for better than half the small/midsize businesses I speak with, is a yearly access control and configuration assessment. No discovery. No monitoring. And if they do logging (and most don't), the data is sent to a log management system and not reviewed. That's it. And apparently lots of big enterprises don't get it right either. We've got tons of really good monitoring, assessment, auditing, masking, and encryption products out there for databases. Some are ridiculously simple to use. Others are offered for free; if you only have a handful of databases, you're not even going to pay to use some of the capabilities.

If database security is nagging at the back of your mind, then take some time and see what's out there. And if you are worried about risks, run a quick analysis to see what assets pose the greatest risk to your firm should they be lost or stolen. I think you will find the contents of the database to be at the top of your list.

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
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/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
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
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-2019-19750
PUBLISHED: 2019-12-12
minerstat msOS before 2019-10-23 does not have a unique SSH key for each instance of the product.
CVE-2019-4606
PUBLISHED: 2019-12-12
IBM DB2 High Performance Unload load for LUW 6.1 and 6.5 could allow a local attacker to execute arbitrary code on the system, caused by an untrusted search path vulnerability. By using a executable file, an attacker could exploit this vulnerability to execute arbitrary code on the system. IBM X-For...
CVE-2019-16246
PUBLISHED: 2019-12-12
Intesync Solismed 3.3sp1 allows Local File Inclusion (LFI), a different vulnerability than CVE-2019-15931. This leads to unauthenticated code execution.
CVE-2019-17358
PUBLISHED: 2019-12-12
Cacti through 1.2.7 is affected by multiple instances of lib/functions.php unsafe deserialization of user-controlled data to populate arrays. An authenticated attacker could use this to influence object data values and control actions taken by Cacti or potentially cause memory corruption in the PHP ...
CVE-2019-17428
PUBLISHED: 2019-12-12
An issue was discovered in Intesync Solismed 3.3sp1. An flaw in the encryption implementation exists, allowing for all encrypted data stored within the database to be decrypted.