News

Oracle Databases Go Unpatched, Survey Finds

• By Kurt Mackie
• January 15, 2008

Oracle typically releases its Critical Patch Updates on a quarterly basis, but these patches apparently are too much of a hassle to apply.

Sentrigo has had informal discussions with IT personnel on the matter, apart from the survey, according to Rani Osnat, Sentrigo's vice president of marketing. The reluctance to patch may stem from all of the testing and downtime that needs to happen before applying Oracle Critical Patch Updates.

"In the case of smaller companies, the DBAs simply don't have time to do it," Osnat said. "In the larger companies, you may have thousands of databases and you literally need to cycle through them to schedule downtime for all of them."

Woburn, Mass.-based Sentrigo collected the responses of 305 Oracle Users Group members in a survey that was conducted from August 2007 to January 2008. Responses were gathered across the various cities where Oracle Users Group meetings were held.

The survey found that only 10 percent (31 people) of the total number of respondents said that they had installed the latest Oracle Critical Patch Updates.

Moreover, 67.5 percent of respondents had never applied any Oracle Critical Patch Updates, according to an announcement issued by Sentrigo.

Sentrigo offers a kind of stop-gap measure to this dilemma. The company's Hedgehog solution uses a technology that Osnat calls "virtual patching."

"The idea of virtual patching is that you have a security layer that monitors the database and all transactions and looks for activities that target vulnerabilities," Osnat explained. "It looks for exploits and issues an alert. The benefit is that it doesn't require any downtime."

Virtual patching is a warning system, and it doesn't solve the root problem. A patch is still needed, eventually.

"We don't recommend it as a substitute for real patching," Osnat said. "On the other hand, most people don't do patching, so this allows them to fill in the gaps in terms of security."

Oracle's last quarterly Critical Patch Update, dated January 2008, addressed 26 new fixes across Oracle Database products.

Osnat explained that many of the vulnerabilities that have been found in Oracle Database have typically allowed SQL injection attacks. It's a method of using the main door of the SQL engine to execute commands, and these commands are then used for privilege escalation. The less severe attacks allow one to gain DBA access privileges via a login and password, but the more severe ones let anyone gain those privileges, he said.

Sentrigo's dismal survey results have an explanation, according to Osnat.

"Database security is not a major priority among IT security folks," he said. "Mostly, we think it's because of their lack of knowledge about databases and what kind of risk database vulnerabilities pose. Most IT security people are more familiar with network security or operating systems -- not so much about databases."

In addition to supporting Oracle Database security, Sentrigo is currently working on releasing a Microsoft SQL Server version that will be available next month, Osnat said. The company plans to start supporting IBM DB2 and Sybase database management systems later this year, he added.

Oracle itself hasn't remained quiet when it comes to issuing warnings about database security.

An official Oracle blog by Chad Hughes, "Getting Started With a Secure Configuration Effort," flagged a number of potential database security problems. For instance, IT professionals incorrectly assume that databases are shielded by corporate firewalls. Moreover, vulnerable databases can be found via Google searches and can be attacked over the Internet, according to Hughes' blog.

Hughes also warns against internal database security threats from personnel. A company may have its security hardened on the outside, but poor security within.