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.

Vulnerabilities / Threats

11/19/2009
04:08 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

New IBM Database Flaw Could Affect Several Other Vendors' Products

Denial-of-service (DoS) attack vulnerability in IBM's SolidDB affects HP OpenView

It turns out a newly discovered vulnerability found and reported in HP OpenView was really a bug in an IBM relational database product deployed in OpenView -- and the vulnerability could affect many other applications that also use the so-called IBM SolidDB technology in their products.

Core Security said it found an exploitable bug in the database server core component of IBM's Solid DB, a caching database technology that basically speeds up application and database performance by offering the database in memory. The vulnerability would allow an attacker to execute a denial-of-service attack against the database service by sending a packet with an invalid error code number in it.

HP this week patched the vulnerability, which affects its OpenView Network Node Manager product, and IBM last Friday patched SolidDB with SolidDB/Universal Cache 6.3 Fix Pack 3. So far, it's unclear whether products from Cisco, HP, Alcatel, Nokia Siemens, IBM DB2, Microsoft SQL Server, Oracle, and Informix that include SolidDB are also definitely vulnerable to the DoS attack. The flaw lies in IBM SolidDB Server versions 6.30.0.29 and 6.30.0.33.

"What started as a single product turned out to be a much bigger issue," says Ivan Arce, CTO for Core, which discovered the IBM SolidDB flaw after HP ruled out the flaw in its own code. "Had we not moved on in our investigating it [further], it may have gone completely unnoticed."

The incident reflects the long arm of a vulnerability when it spans multiple vendors' products. But it's not the first time one vendor's vulnerability has affected other vendors' products. John Pescatore, vice president and distinguished analyst at Gartner, says Microsoft's recent graphics-handling library vulnerabilty, as well as a previous IIS bug that affected Cisco routers, are two examples of one vendor's bug creating a domino effect on others' products.

"This is a pre-Service Oriented Architecture [SOA] example of the risks" in software components being used in different places over and over, he says. "Think about the Google components you can mash up with your own apps. If there's a vulnerability in one of those components and they get reused in thousands of places," the vulnerability becomes more widespread, he says.

That makes patching difficult, too. "IBM made the patch available, but it can't patch other vendors' software," he says.

Core says the IBM bug could ultimately impact many other products. According to IBM, there are more than 3 million SolidDB deployments spanning telecommunications networks, enterprise applications, and embedded software and systems. That means those products are also vulnerable to a DoS attack exploiting this bug, according to Core. The trouble with a vulnerability that spans multiple vendors' products is that coordination can be complicated, Arce says. Whichever vendor discovers the bug has to contact the other or others. "The two vendors may have different development cycles and skills," he says. "And patching is relatively more complicated."

Customers of products that contain SolidDB should first check how integrated it is in the product. "See if it's open to requests to the network and if it's vulnerable or not" to the attack, Arce says. And apply the IBM patch, he says.

The good news is that the bug is only exploitable as a DoS attack, he says, and nothing more. And Core has not seen any exploits in the wild, Arce says.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message. Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... 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-19782
PUBLISHED: 2019-12-13
The FTP client in AceaXe Plus 1.0 allows a buffer overflow via a long EHLO response from an FTP server.
CVE-2019-19777
PUBLISHED: 2019-12-13
stb_image.h (aka the stb image loader) 2.23, as used in libsixel and other products, has a heap-based buffer over-read in stbi__load_main.
CVE-2019-19778
PUBLISHED: 2019-12-13
An issue was discovered in libsixel 1.8.2. There is a heap-based buffer over-read in the function load_sixel at loader.c.
CVE-2019-16777
PUBLISHED: 2019-12-13
Versions of the npm CLI prior to 6.13.4 are vulnerable to an Arbitrary File Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a serve binary, any subsequent installs of pa...
CVE-2019-16775
PUBLISHED: 2019-12-13
Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It is possible for packages to create symlinks to files outside of thenode_modules folder through the bin field upon installation. A properly constructed entry in the package.json bin field would allow a package publi...