Application Security, Inc.
home client login partner login online store contact us
search:
Solutions Products Partners Support News & Events About Us

Team SHATTER Security Advisory

IBM DB2 Buffer overflow in sysproc.auth_list_groups_for_authid

Aug 31, 2007 (Updated Sept. 7th 2007)

Risk Level:
High

Affected versions:
DB2 9 on all platforms

Remote exploitable:
Yes (Authentication to Database Server is needed)

Credits:
This vulnerability was discovered and researched by Ariel Sanchez of Application Security Inc.

Details:
Buffer overflow on sysproc.auth_list_groups_for_authid function.
By passing an overly long value of more then 30-bytes to the auth_list_groups_for_authid function,
a stack-based buffer can be overflowed.
The AUTH_LIST_GROUPS_FOR_AUTHID function is installed by default.

Impact:
Any low privileged user can exploit this vulnerability to cause a denial of service or to run arbitrary code. On Windows systems, the attacker may take complete control of the affected system because DB2 service runs under an administrative account.

Vendor Status:
Vendor was contacted and a patch was released.

Fix:
To fix the problem apply the fixpak 3 for DB2 version 9.1
http://www-306.ibm.com/software/data/db2/support/db2_9/

APAR:
IZ01828

Links:
Application Security, Inc advisory: http://www.appsecinc.com/resources/alerts/db2/2007-01.shtml
IBM APAR: http://www-1.ibm.com/support/docview.wss?uid=swg1IZ01828

--
_____________________________________________
Copyright © 2007 Application Security, Inc.
http://www.appsecinc.com


Application Security, Inc’s database security solutions have helped over 900 organizations secure their databases from all internal and external threats
while also ensuring that those organizations meet or exceed regulatory compliance and audit requirements.


Disclaimer: The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use
of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the
author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.