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

Ovum says ad hoc tools are out-dated. The best practice approach?
Fast vulnerability intelligence, threat handling, and setup in one tool.

Read the new report on the Secunia VIM:
http://secunia.com/products/corporate/vim/ovum_2011_request/ 

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

TITLE:
KaiBB Two SQL Injection Vulnerabilities

SECUNIA ADVISORY ID:
SA46276

VERIFY ADVISORY:
Secunia.com
http://secunia.com/advisories/46276/
Customer Area (Credentials Required)
https://ca.secunia.com/?page=viewadvisory&vuln_id=46276

RELEASE DATE:
2011-10-15

DISCUSS ADVISORY:
http://secunia.com/advisories/46276/#comments

AVAILABLE ON SITE AND IN CUSTOMER AREA:
 * Last Update
 * Popularity
 * Comments
 * Criticality Level
 * Impact
 * Where
 * Solution Status
 * Operating System / Software
 * CVE Reference(s)

http://secunia.com/advisories/46276/

ONLY AVAILABLE IN CUSTOMER AREA:
 * Authentication Level
 * Report Reliability
 * Secunia PoC
 * Secunia Analysis
 * Systems Affected
 * Approve Distribution
 * Remediation Status
 * Secunia CVSS Score
 * CVSS

https://ca.secunia.com/?page=viewadvisory&vuln_id=46276

ONLY AVAILABLE WITH SECUNIA CSI AND SECUNIA PSI:
 * AUTOMATED SCANNING

http://secunia.com/vulnerability_scanning/personal/
http://secunia.com/vulnerability_scanning/corporate/wsus_sccm_3rd_third_party_patching/

DESCRIPTION:
Two vulnerabilities have been discovered in KaiBB, which can be
exploited by malicious people to conduct SQL injection attacks.

1) Input passed via the "forum" parameter to rss.php is not properly
sanitised before being used in SQL queries. This can be exploited to
manipulate SQL queries by injecting arbitrary SQL code.

Successful exploitation of this vulnerability requires that
"magic_quotes_gpc" is disabled.

2) Input appended to the URL after e.g. index.php is not properly
sanitised in inc/header.php before being used in SQL queries. This
can be exploited to manipulate SQL queries by injecting arbitrary SQL
code.

Note: This vulnerability can further be exploited to conduct
cross-site scripting attacks via SQL error messages.

The vulnerabilities are confirmed in version 2.0.1. Other versions
may also be affected.

SOLUTION:
Edit the source code to ensure that input is properly sanitised.

PROVIDED AND/OR DISCOVERED BY:
Independently discovered by Morten Bartvig, Secunia and Stefan
Schurtz.

ORIGINAL ADVISORY:
Secunia Research:
http://secunia.com/secunia_research/2011-72/

SSCHADV2011-027:
http://www.rul3z.de/advisories/SSCHADV2011-027.txt

OTHER REFERENCES:
Further details available in Customer Area:
http://secunia.com/vulnerability_intelligence/

DEEP LINKS:
Further details available in Customer Area:
http://secunia.com/vulnerability_intelligence/

EXTENDED DESCRIPTION:
Further details available in Customer Area:
http://secunia.com/vulnerability_intelligence/

EXTENDED SOLUTION:
Further details available in Customer Area:
http://secunia.com/vulnerability_intelligence/

EXPLOIT:
Further details available in Customer Area:
http://secunia.com/vulnerability_intelligence/

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

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

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

Definitions: (Criticality, Where etc.)
http://secunia.com/advisories/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.

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