History of Vulnerability Report Status
| Version 3 | Current version | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
This page lists vulnerability reports – concerning the security of the Bitweaver application – posted on websites other than bitweaver.org, in order to address and to discuss outstanding issues, and to identify their current status. During and after the installation of Bitweaver, a user chooses to activate a sub-set of all available packages, modules, features, input formats, etc. A report on a security issues might be based on an unattended install, before the security recommendations were considered. A site with different settings may not be affected. As an example, a site configured to restrict input of data to wiki syntax will not be affected by HTML vulnerabilities. Identifying and discussing these reports is necessary, because they might have one or all of the following problems:
List of reports
Report: Multiple XSSThe report named Multiple Cross-site Scripting Vulnerabilities has been duplicated across several sites, some of which do not list the concerned pages. The Secunia report has a list of pages that can be tested. In current versions of Bitweaver, these security issues have been fixed. They are all now handled correctly. For the original report, see Secunia Advisory: SA32014To test if an install is compromised by the exploit, the string <script>alert('hi!');</script> can be used. Bitweaver version 2 and above prevent the creation of persistent XSS attacks, so the above script can not be stored within this page and will need to be added manually to the address bar of your browser. The string will be returned with the tag characters converted to %xx equivalents. Below is a list of PHP files of Bitweaver version 1.3 and below that are expected to be vulnerable to XSS-attacks. As the problem has been addressed within the core processing of Bitweaver, from version 2 on, these files and any other files, even if not listed here, are now considered to be immune against this exploit.
Further search resultsCVE Listing 18 entries back to 2005, mainly XSSSecunia Listing 7 entries sub set of CVE XForce (IBM ISS) Listing 19 entries - not spotted the extra one over CVE | This page lists vulnerability reports – concerning the security of the Bitweaver application – posted on websites other than bitweaver.org, in order to address and to discuss outstanding issues, and to identify their current status. During and after the installation of Bitweaver, a user chooses to activate a sub-set of all available packages, modules, features, input formats, etc. A report on a security issues might be based on an unattended install, before the security recommendations were considered. A site with different settings may not be affected. As an example, a site configured to restrict input of data to wiki syntax will not be affected by HTML vulnerabilities. Identifying and discussing these reports is necessary, because they might have one or all of the following problems:
List of reports
Report: Multiple XSSThe report named Multiple Cross-site Scripting Vulnerabilities has been duplicated across several sites, some of which do not list the concerned pages. The Secunia report has a list of pages that can be tested. In current versions of Bitweaver, these security issues have been fixed. They are all now handled correctly. For the original report, see Secunia Advisory: SA32014To test if an install is compromised by the exploit, the string
Further search resultsCVE Listing 18 entries back to 2005, mainly XSSSecunia Listing 7 entries sub set of CVE XForce (IBM ISS) Listing 19 entries - not spotted the extra one over CVE |