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

6/21/2010
08:53 PM
Adrian Lane
Adrian Lane
Commentary
50%
50%

Open-Source Database Security

A recent article on Dark Reading underscores a growing concern in IT: how to secure open-source databases.

A recent article on Dark Reading underscores a growing concern in IT: how to secure open-source databases.According to the article, "Open-Source Databases Pose Unique Security Challenges," by Ericka Chickowski, Ingres and MySQL are being used for large-scale commercial applications. They support Web commerce sites and are growing in use as fast as their commercial counterparts. They are used as a replacement for Oracle, DB2, and SQL Server when cost or flexibility is an issue. The issue Ericka raises is not that these platforms are less secure by nature, but that they lack the supporting security knowledge and tools available on other platforms.

Until recently, the major database vendors did not offer a full suite of database security options. Now they do, with activity monitoring, assessment, and transparent encryption to go along with access controls and authorization schemes. Rummage around the open-source Web sites and you will discover deployment guides and basic security tips -- but these center around access controls and secure communication (i.e., SSL). Security research and tools designed to help secure these platforms is generally absent. Third-party vendors have not ported their monitoring, masking, auditing, and assessment tools because customer demand has not been high enough to justify the costs.

To get a better idea of why this is important, let's look at vulnerability assessment. There are no formalized assessment products, and beyond a smattering of policies for MySQL, no research teams perform policy development for open-source databases.

1. Research for threats, remediation and workarounds: DBAs for the most part are not security professionals, they don't spend their days researching security threats, and they don't know what to look for. What does the attack look like? What is a suitable resolution? Are patches available? If not, is there a workaround/resolve the issue?

2. Automation for the collection of user permissions, manual comparison of settings in relation to established policies, and keeping up to date with patches are all time-consuming, mistake-prone process.

3. Writing the queries to find the information is time-consuming. One of the aspects I hated most about creating assessment policies was writing the queries as a simple check, which could take a day to write and optimize, then test it across all revisions of the database. It might be cost-effective for very large firms to do, but small security firms have trouble justifying the cost of this development.

Apache Derby, Open Ingres, MySQL, and Postgres (or PostgreSQL for some of you) have millions of databases in use. Look at the vendor best practices guides and you will see a preponderance of the discussion around access control and use of SSL. Advanced security usually falls onto the shoulders of the application developers to thwart SQL injection and memory exploits. There are few generic tools over and above file/OS encryption, and that only addresses media protection. Only MySQL has support for monitoring, assessment, third-party auditing, blocking, advanced configuration guides and the like. The other databases? Not so much.

I don't bring this up as some form of advertisement for tools and tool vendors because, frankly, the security vendors don't make solutions for these platforms. My point is to illustrate that security goes largely unaddressed, offering something of a greenfield for attackers. And while we don't hear about these attacks, they do happen.

Is it time for the open-source community to build security policies? Probably. Will it happen? I doubt it. Heck, I can't even find good tuning and performance guide for Postrges: It took years of speaking to other DBAs, along with trial and error, before I found what worked. And believe me, performance questions are far more common than security questions. There is not enough customer demand to motivate third parties or vendors to invest in development. As use of these platforms increases, especially as low-cost, cloud-based services, attacks will increase in frequency, much as they have with Oracle and SQL Server. Unless the open-source community steps up, the platforms will likely suffer a black eye before things change.

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
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...