----------------------------------------------------------------------

To improve our services to our customers, we have made a number of
additions to the Secunia Advisories and have started translating the
advisories to German.

The improvements will help our customers to get a better
understanding of how we reached our conclusions, how it was rated,
our thoughts on exploitation, attack vectors, and scenarios.

This includes:
* Reason for rating
* Extended description
* Extended solution
* Exploit code or links to exploit code
* Deep links

Read the full description:
http://corporate.secunia.com/products/48/?r=l

Contact Secunia Sales for more information:
http://corporate.secunia.com/how_to_buy/15/?r=l

----------------------------------------------------------------------

TITLE:
Borland Products idsql32.dll Buffer Overflow Vulnerability

SECUNIA ADVISORY ID:
SA22570

VERIFY ADVISORY:
http://secunia.com/advisories/22570/

CRITICAL:
Moderately critical

IMPACT:
System access

WHERE:
>From remote

SOFTWARE:
Borland Delphi 2006
http://secunia.com/product/12772/
Borland C++ Builder 2006
http://secunia.com/product/12771/
Borland C# Builder 2006
http://secunia.com/product/12773/
Borland C++ Builder 5.x
http://secunia.com/product/1584/
Borland C++Builder 6.x
http://secunia.com/product/8350/
Borland Delphi 5.x
http://secunia.com/product/8911/
Borland Delphi 6.x
http://secunia.com/product/10297/
Borland Delphi 7.x
http://secunia.com/product/8598/

DESCRIPTION:
Secunia Research has discovered a vulnerability in Borland products,
which can be exploited by malicious people to compromise a vulnerable
system.

The vulnerability is caused due to a boundary error in idsql32.dll
when processing SQL statements using the "DbiQExec()" function. This
can be exploited to cause a heap-based buffer overflow via an overly
long SQL statement (more than 4000 bytes).

Successful exploitation may allow execution of arbitrary code.

The vulnerability is confirmed in idsql32.dll versions 5.1.0.4 and
5.2.0.2. Other versions may also be affected. Also, any application
or service using the vulnerable library may also be affected.

SOLUTION:
Restrict access to applications and services using the vulnerable
library.

Applications using the vulnerable library should check the length of
the user input before creating an SQL statement and using it in a
query.

PROVIDED AND/OR DISCOVERED BY:
JJ Reyes, Secunia Research

ORIGINAL ADVISORY:
Secunia Research:
http://secunia.com/secunia_research/2006-70

----------------------------------------------------------------------

About:
This Advisory was delivered by Secunia as a free service to help
everybody keeping their systems up to date against the latest
vulnerabilities.

Subscribe:
http://secunia.com/secunia_security_advisories/

Definitions: (Criticality, Where etc.)
http://secunia.com/about_secunia_advisories/


Please Note:
Secunia recommends that you verify all advisories you receive by
clicking the link.
Secunia NEVER sends attached files with advisories.
Secunia does not advise people to install third party patches, only
use those supplied by the vendor.

----------------------------------------------------------------------

Unsubscribe: Secunia Security Advisories
http://secunia.com/sec_adv_unsubscribe/?email=packet%40packetstormsecurity.org

----------------------------------------------------------------------