Confluence Docs 3.0 : Confluence Security Advisory 2009-06-16 This page last changed on Jun 16, 2009 by ggaskell. In this advisory: Page Content Vulnerabilities Severity Risk Assessment Risk Mitigation Vulnerability Fix ## Page Content Vulnerabilities
| If you have already upgraded to Confluence 3.0, then you are not affected by the vulnerabilities described on this page and there is no need to take any further action.
#### Severity Atlassian rates these vulnerabilities as high, according to the scale published in Confluence Security. The scale allows us to rank a vulnerability as critical, high, moderate or low. #### Risk Assessment We have identified and fixed two security vulnerabilities which may affect Confluence instances in a public environment. Both of these fixes are associated with a tightening of user access restrictions when either viewing specific page content or adding new page content. The first of these vulnerabilities allows a user without permission to view a given page, to view the contents of any files attached to that page using the view file macro. This assumes that the user has permission to edit or create another page within the Confluence site and knows the name of the file attached to the page they cannot view. For more information, please refer to the JIRA issue CONF-15809. The second of these vulnerabilities allows users with space administrator permissions to import pages to a Confluence space. The security level of this function has been tightened to permit only users with the system administration permission to access it. For more information, please refer to CONF-15267. #### Risk Mitigation If you have not already upgraded to Confluence 3.0, then we recommend either patching or upgrading your Confluence installation to fix these vulnerabilities. Please see the 'Fix' section below. Alternatively, if you are not in a position to undertake this immediately and you judge it necessary, you can disable public access (e.g. anonymous access and public sign-on) to your wiki until you have applied the necessary patch or upgrade. For even tighter control, you could restrict access to trusted groups. #### Vulnerability All versions of Confluence up to and including version 2.10.3 with the Office Connector plugin installed are affected by the first view file macro vulnerability. All versions of Confluence 2.10.x are affected by the second page imports vulnerability. #### Fix These issues have been fixed in Confluence 3.0 (see the release notes), which you can download from the download centre. If you do not wish to upgrade to Confluence 3.0, you can download and install the patches provided on our JIRA site. You will need to upgrade to the latest point release for the major version of Confluence that you are running (e.g. if you are running Confluence 2.10.0, you will need to upgrade to version 2.10.3) and then apply the patches. For more information, please refer to the specific JIRA issues shown below. To download the patch to fix the first view file macro vulnerability, please refer to CONF-15809. To download the patch to fix the second page import vulnerability, please refer to CONF-15267.

Document generated by Confluence on Nov 05, 2009 23:27