History of Security
| Version 3 | Current version | |
|---|---|---|
Security settingsAfter you installed Bitweaver, check the following settings:
Security issuesCode injection into contentA malicious user might try to input code through on of Bitweaver's content forms (comment, wiki page etc). The best way to prevent susceptibility to HTML hacking is to disable HTML as an input format. As the Bitweaver framework allows a number of formats for content, using a wiki type format while not allowing HTML is the most secure option. It's also possible to allow HTML only for certain user groups (admins, editors etc).If the flexibility of using HTML outweighs the security concerns, Bitweaver provides a number of additional tools to sanitise data entry. One advanatge of HTML is the availability of WYSIWYG editors like FCKeditor or TinyMCE. Both of these provide filtering of input, such as only allowing a sub set of HTML tags. Since it is possible to bypass the editors to enter HTML, a more serious level of filtering is provided by Bitweaver's Simple HTML Purifier. Finally, the most secure and comprehensive option is to use HTMLPurifier. SQL injectionA malicious user might try to inject code into the SQL database (Postgres, MySQL etc). Each database engine requires a different version of an attack to present viable SQL. Invalid SQL will result in an error report to the administrator. A 'White Screen', claiming that you are running Bitweaver in test mode, is only returned when the parameterIS_LIVE set to TRUE in kernel/config_inc.php. Sites being in production are expected to have set this to FALSE, while error reports are directed to appropriate error log files.In the past, some of Bitweaver's search functions allowed the inclusion of additional SQL WHERE clauses. This was not database agnostic and has been replaced. Now, additional search options build the SQL internally, preventing any possible injection attack.wiki_url_importThe "suck_url Information Disclosure" security issue has been fixed in version 2.1. Before, it was exploitable when the admin had enabled the feature wiki_url_import (default: disabled).Hacking attemptsThe script kiddie plague du jour is the idea to exploit code that does:include($varWithSomeUrlFromGetString); which would execute remotely written PHP. If such an attack is attemped, a Bitweaver install might mail an error message to you, the admin, alerting an "unknown column" or "unknown sort order" (note that normal users browsing your pages will never see any error message unless you set IS_LIVE to false in /kernel/config_inc.php). The error mail informs you that the attemptet hack failed (that it didn't do anything). See SQL injection above.PHP security settings
Earlier Bitweaver versionsBitweaver versions 1.3 and before were released in 2004/2005 (see bitweaverRoadMap). These versions are not supported anymore, i.e., the code hasn't been updated since the release. There are a couple of serious security issues. Some stem from 3rd party code, like left-over code from older versions, as well as the infamous XMLRPC bug (if enabled). Many of the improvements introduced with Bitweaver 2 addressed these issues specifically. In other words, don't install version 1.3. If you're running version 1.3 and are concerned about security, please upgrade Bitweaver.Vulnerability Reportslinks (wip) | Security settingsAfter you installed Bitweaver, check the following settings:
Security issuesCode injection into contentA malicious user might try to input code through on of Bitweaver's content forms (comment, wiki page etc). The best way to prevent susceptibility to HTML hacking is to disable HTML as an input format. As the Bitweaver framework allows a number of formats for content, using a wiki type format while not allowing HTML is the most secure option. It's also possible to allow HTML only for certain user groups (admins, editors etc).If the flexibility of using HTML outweighs the security concerns, Bitweaver provides a number of additional tools to sanitise data entry. One advanatge of HTML is the availability of WYSIWYG editors like FCKeditor or TinyMCE. Both of these provide filtering of input, such as only allowing a sub set of HTML tags. Since it is possible to bypass the editors to enter HTML, a more serious level of filtering is provided by Bitweaver's Simple HTML Purifier. Finally, the most secure and comprehensive option is to use HTMLPurifier. SQL injectionA malicious user might try to inject code into the SQL database (Postgres, MySQL etc). Each database engine requires a different version of an attack to present viable SQL. Invalid SQL will result in an error report to the administrator. A 'White Screen', claiming that you are running Bitweaver in test mode, is only returned when the parameterIS_LIVE set to FALSE in kernel/config_inc.php. Sites being in production are expected to have set this to TRUE, while error reports are directed to appropriate error log files.In the past, some of Bitweaver's search functions allowed the inclusion of additional SQL WHERE clauses. This was not database agnostic and has been replaced. Now, additional search options build the SQL internally, preventing any possible injection attack.wiki_url_importThe "suck_url Information Disclosure" security issue has been fixed in version 2.1. Before, it was exploitable when the admin had enabled the feature wiki_url_import (default: disabled).Hacking attemptsThe script kiddie plague du jour is the idea to exploit code that does:include($varWithSomeUrlFromGetString); which would execute remotely written PHP. If such an attack is attemped, a Bitweaver install might mail an error message to you, the admin, alerting an "unknown column" or "unknown sort order" (note that normal users browsing your pages will never see any error message unless you set IS_LIVE to false in /kernel/config_inc.php). The error mail informs you that the attemptet hack failed (that it didn't do anything). See SQL injection above.PHP security settings
Earlier Bitweaver versionsBitweaver versions 1.3 and before were released in 2004/2005 (see bitweaverRoadMap). These versions are not supported anymore, i.e., the code hasn't been updated since the release. There are a couple of serious security issues. Some stem from 3rd party code, like left-over code from older versions, as well as the infamous XMLRPC bug (if enabled). Many of the improvements introduced with Bitweaver 2 addressed these issues specifically. In other words, don't install version 1.3. If you're running version 1.3 and are concerned about security, please upgrade Bitweaver.Vulnerability ReportsA discussion of 3rd party Vulnerability Reports on the security of Bitweaver can be found on the page Vulnerability Report Status. |