Multiple vulnerabilities have been reported in DB2 Universal Database, where some of the vulnerabilities have an unknown impact and others can be exploited to gain knowledge of various information, cause a DoS (Denial of Service), gain escalated privileges, or compromise a vulnerable system.

1) Unspecified boundary errors exist, which can be exploited to cause buffer overflows and may allow execution of arbitrary code.

2) An input validation error within the DB2 security service can be exploited to crash it by sending specially crafted data.

3) An access control error makes it possible for users to signal the DB2 UDB instance to shut down.

4) A boundary error within the handling of library names can be exploited to cause a stack-based buffer overflow by passing an overly long library name.

Successful exploitation allows execution of arbitrary code.

5) A boundary error within the satellite user-defined function SATADMIN.SATENCRYPT can be exploited to cause a stack-based buffer overflow by passing an overly long parameter.

6) A boundary error within the JDBC listener Applet Server can be exploited to cause a stack-based buffer overflow by connecting multiple times with specially crafted usernames.

7) Errors within some XML functions can be exploited to read or write arbitrary files on the system with the privileges of the account running DB2.

8) A boundary error in the libdb2.so.1 library within the handling of the "DB2LPORT" environment variable can be exploited by malicious, local users to cause a buffer overflow and execute arbitrary code with escalated privileges via applications linked against the vulnerable library (e.g. db2cacpy installed setuid "root").

9) A boundary error within the db2fmp utility can be exploited by malicious, local users to cause a buffer overflow and execute arbitrary code with "root" privileges by passing an overly long command line argument.

10) Boundary errors within some XML functions can be exploited to cause stack-based buffer overflows by passing overly long parameters.

11) NULL pointer dereference errors in the "to_char()" and "to_date()" functions can be exploited to cause a DoS when called with empty parameters.

12) Improper permissions for the "everyone" group on Windows systems makes it possible to access certain DB2 resources (shared memory sections and events), which should not be possible. This can be exploited to disclose various information (including usernames and passwords) or cause a DoS.

Solution
Apply DB2 FixPak 6a or 7a.
Further details available to Secunia VIM customers

Provided and/or discovered by
1-3) Reported by vendor.
4-10) David Litchfield, NGSSoftware.
11, 12) Chris Anley, NGSSoftware.

Changelog
Further details available to Secunia VIM customers

Original Advisory
IBM:
http://www-1.ibm.com/support/docview.wss?uid=swg21179535
http://www-1.ibm.com/support/docview.wss?uid=swg21181105
http://www-1.ibm.com/support/docview.wss?uid=swg21181228
http://www-1.ibm.com/support/docview.wss?uid=swg24007489
http://www-1.ibm.com/support/docview.wss?uid=swg24007670
http://www-1.ibm.com/support/docview.wss?uid=swg1IY60622

NGSSoftware:
http://www.nextgenss.com/advisories/db205012005A.txt
http://www.nextgenss.com/advisories/db205012005B.txt
http://www.nextgenss.com/advisories/db205012005C.txt
http://www.nextgenss.com/advisories/db205012005D.txt
http://www.nextgenss.com/advisories/db205012005E.txt
http://www.nextgenss.com/advisories/db205012005F.txt
http://www.nextgenss.com/advisories/db205012005G.txt
http://www.nextgenss.com/advisories/db205012005H.txt
http://www.nextgenss.com/advisories/db205012005I.txt

Deep Links
Links available to Secunia VIM customers