SYMSA-2007-014: SQL Injection Vulnerability in Beehive Forum Software

2007-12-05T00:00:00
ID SECURITYVULNS:DOC:18559
Type securityvulns
Reporter Securityvulns
Modified 2007-12-05T00:00:00

Description

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

                 Symantec Vulnerability Research
                 http://www.symantec.com/research
                       Security Advisory

Advisory ID: SYMSA-2007-014 Advisory Title: SQL Injection Vulnerability in Beehive Forum Software Author: Nick Bennett Robert Brown / robert_brown@symantec.com Release Date: 28-11-2007 Application: Beehive Forum 0.7.1 (earlier versions also vulnerable) Platform: All supported Severity: Remotely exploitable / Information Disclosure Vendor status: Updated Application Versions Available CVE Number: CVE-2007-6014 Reference: http://www.securityfocus.com/bid/26492

Overview:

Beehive Forum is an open source web based forum application written in PHP. A vulnerability exists in the Beehive Forum software that could allow a remote user to execute SQL injection attacks. These attacks could compromise sensitive data including usernames and passwords for the Beehive application. Arbitrary data from other applications hosted on the same server could also be compromised, depending on the configuration of MySQL.

Details:

This vulnerability exists because of a failure in the application to properly sanitize user input for the variable "t_dedupe". This variable is accepted as input in the page "post.php". The value of this variable is then included in an SQL statement which is executed with the PHP function "@mysql_query". This function is specifically designed to mitigate the effects of an SQL injection attack by not allowing multiple SQL statements in one call. However, it is still possible to manipluate the SQL statement through the "t_dedupe" variable to obtain arbitrary data from the database.

Vendor Response:

There is a security vulnerability in Beehive Forum that could allow for user logon and password MD5 hash disclosure.

This vulnerability has been fixed in the latest release of the product, Beehive Forum 0.8. It is recommend all users immediately obtain the newest version of Beehive Forum to protect against this threat.

Project Beehive Forum is available for download from the project website at http://www.beehiveforum.net/

If there are any further questions about this statement, please contact a member of the development team.

Recommendation:

It is recommend all users immediately obtain the newest version of Beehive Forum to protect against this threat. Project Beehive Forum is available for download from the project website at http://www.beehiveforum.net/.

Common Vulnerabilities and Exposures (CVE) Information:

The Common Vulnerabilities and Exposures (CVE) project has assigned the following names to these issues. These are candidates for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems.

CVE-2007-6014

  • ----------Symantec Vulnerability Research Advisory Information-------

For questions about this advisory, or to report an error: research@symantec.com

For details on Symantec's Vulnerability Reporting Policy: http://www.symantec.com/research/Symantec-Responsible-Disclosure.pdf

Symantec Vulnerability Research Advisory Archive: http://www.symantec.com/research/

Symantec Vulnerability Research GPG Key: http://www.symantec.com/research/Symantec_Vulnerability_Research_GPG.asc

  • ----------------Symantec Product Advisory Information-------------

To Report a Security Vulnerability in a Symantec Product: secure@symantec.com

For general information on Symantec's Product Vulnerability reporting and response: http://www.symantec.com/security/

Symantec Product Advisory Archive: http://www.symantec.com/avcenter/security/SymantecAdvisories.html

Symantec Product Advisory PGP Key: http://www.symantec.com/security/Symantec-Vulnerability-Management-Key.asc


Copyright (c) 2007 by Symantec Corp. Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Consulting Services. Reprinting the whole or part of this alert in any medium other than electronically requires permission from research@symantec.com.

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.

Symantec, Symantec products, and Symantec Consulting Services are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32)

iD8DBQFHVFXyuk7IIFI45IARAhJqAKCGc/4L5tb0bq1s1jrp6mwEFJBBRgCcDA+F V7igvapHPpck2rZdZRlgB0Q= =JzzL -----END PGP SIGNATURE-----