Application Security Inc. - Database Security, Monitoring, Assessment, Auditing, Encryption, and Regulatory Compliance.
 
 
 
home client login partner login purchasing info contact us
search:
Solutions Products Partners Support News & Events About Us

Team SHATTER Security Advisory

Buffer overrun in XMLQUERY and XMLEXISTS

September 15th 2008

Risk Level:
High

Affected versions:
IBM DB2 Database Server v9.1 and 9.5 on Windows platform.

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

Credits:
These vulnerabilities were discovered and researched by Ariel Sanchez of Application Security Inc.

Details:
The XMLQUERY and XMLEXISTS functions are vulnerable to a stack based buffer overflow by passing an overly long parameter. The XMLQUERY and XMLEXISTS functions are installed by default.

Impact:
Any low privileged user can exploit these vulnerabilities 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 FP5(v9.1)and FP1(v9.5):
http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg24019146
http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg21287889

CVE:
CVE-2008-3854

APAR:
IZ18434 - V9.1 FP5
IZ18431 - V9.5 FP1

Timeline:
Vendor Notification - 9/11/2007
Vendor Response - 11/14/2007
Fix - 8/28/2008
Public Disclosure - 9/15/2008


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.