IBM DB2 Universal Database versions 8.1 prior to 8.1 FixPak 14 and 8.2 prior to 8.2 FixPak 7 contain a vulnerability that could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition.
The vulnerability exists due to insufficient filtering on unspecified fields as part of CONNECT requests from version 7 clients within the sqle_db2ra_as_recvrequest function. An unauthenticated, remote attacker could exploit this vulnerability by sending a crafted CONNECT request to the affected server. This could trigger a NULL pointer dereference, crashing the affected server and denying further database access to system applications and users.
IBM confirmed this vulnerability in APARs and corrected
the vulnerability in FixPak 14 for version 8.1, also known as FixPak 7 for version 8.2.
Indicators of Compromise
Systems running IBM DB2 Universal Database versions 8.2 prior to 8.2 FixPak 7 or 8.1 prior to 8.1 FixPak 14 are vulnerable.
Clients initiate connections to DB2 servers using CONNECT commands. The vulnerability exists due to insufficient filtering on SQLJRA packets as part of CONNECT requests from version 7 clients within the sqle_db2ra_as_recvrequest function. This vulnerable function resides within the db2engn.dll library. Malicious CONNECT requests containing crafted SQLJRA values can trigger a NULL pointer dereference, crashing the database service and creating a DoS condition.
Because this vulnerability exists in establishing CONNECT requests prior to authentication, attackers or malicious users do not require authentication credentials to exploit this vulnerability. However, an attacker likely requires access to trusted, internal networks because most database implementations block external connections through a strong firewall policy.
Administrators are advised to apply the appropriate FixPak from IBM.
Administrators are advised to restrict database access to trusted users.
Administrators are advised to protect DB2 servers from direct client access over the Internet by using an appropriate firewall strategy.
Administrators are advised to use IP-based ACLs to allow only authorized hosts to connect to DB2 servers.
THIS DOCUMENT IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM
THE DOCUMENT IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE ALERTS AT ANY TIME.
FIXED SOFTWARE INFORMATION AND LINKS PROVIDED BY SUPPLIERS AND VENDORS ARE FOR REFERENCE ONLY. USERS SHOULD CONTACT THEIR SUPPLIER OR VENDOR FOR UPDATED SOFTWARE.
A standalone copy or paraphrase of the text of this document that omits the distribution URL is an uncontrolled copy and may lack important information or contain factual errors. The information in this document is intended for end users of Cisco products
Cisco Multivendor Vulnerability Alerts respond to vulnerabilities identified in third-party vendors' products. These alerts contain information compiled from diverse sources and provide comprehensive technical descriptions, objective analytical assessments, workarounds and practical safeguards, and links to vendor advisories and patches.