• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest
    • 3.4.5
    • 2.7, 2.8, 2.9, 3.0, 3.1, 3.2, 3.3, 3.4
    • None

      We have identified and fixed a cross-site scripting (XSS) vulnerability in the Confluence

      {pagetree}

      macro.

      XSS vulnerabilities potentially allow an attacker to embed their own JavaScript into a Confluence page. You can read more about XSS attacks at various places on the web, including these:

      This issue is reported in our security advisory on this page:
      http://confluence.atlassian.com/x/HgdrDQ

            [CONFSERVER-21393] XSS vulnerability in Pagetree macro

            VitalyA added a comment -

            Please note that we have released multiple advisories about Confluence 3.2 or later, the earliest advisory - http://confluence.atlassian.com/display/DOC/Confluence+Security+Advisory+2010-05-04. We recommend that you review them and decide whether you can upgrade to a more recent version of the product or apply external security controls if you cannot. Most of the vulnerabilities are not critical and often present less risk when used in a corporate environment with no access from the Internet.

            We usually provide patches only for critical severity (= really bad) vulnerabilities as a stop-gap measure until you can upgrade, and you should not expect that you can continue patching your system instead of upgrading. Our patches are often non-cumulative - we do not recommend that you apply multiple patches from different advisories on top of each other, but strongly recommend to upgrade to the most recent version regularly.

            VitalyA added a comment - Please note that we have released multiple advisories about Confluence 3.2 or later, the earliest advisory - http://confluence.atlassian.com/display/DOC/Confluence+Security+Advisory+2010-05-04 . We recommend that you review them and decide whether you can upgrade to a more recent version of the product or apply external security controls if you cannot. Most of the vulnerabilities are not critical and often present less risk when used in a corporate environment with no access from the Internet. We usually provide patches only for critical severity (= really bad) vulnerabilities as a stop-gap measure until you can upgrade, and you should not expect that you can continue patching your system instead of upgrading. Our patches are often non-cumulative - we do not recommend that you apply multiple patches from different advisories on top of each other, but strongly recommend to upgrade to the most recent version regularly.

            Dave added a comment -

            Will we get a separate fix for 3.2 or the current fix can be used?

            Dave added a comment - Will we get a separate fix for 3.2 or the current fix can be used?

            The patch is simply an updated version of the plugin. Details on how to install a plugin for your version are here.

            You can also find out about using the pagetree macro here.

            Cheers,
            Mark

            Mark Hrynczak (Inactive) added a comment - The patch is simply an updated version of the plugin. Details on how to install a plugin for your version are here . You can also find out about using the pagetree macro here . Cheers, Mark

            AS added a comment -

            Can someone provide the instructions to apply this patch. I am new to confluence and not sure how this will be appplied. BTW I have not seen any file that starts with pagetree* in our environment. We are on 3.3.3.

            AS added a comment - Can someone provide the instructions to apply this patch. I am new to confluence and not sure how this will be appplied. BTW I have not seen any file that starts with pagetree* in our environment. We are on 3.3.3.

            HengHwa Loi [Atlassian] added a comment - - edited

            Tested on 3.1.2, it works!

            Edit: Did a quick test on this, appear to be working to me, but please be aware that this is contradict with the compatibility matrix.

            HengHwa Loi [Atlassian] added a comment - - edited Tested on 3.1.2, it works! Edit: Did a quick test on this, appear to be working to me, but please be aware that this is contradict with the compatibility matrix .

            uvoellger added a comment -

            Any information about 3.3.1?
            Thanks

            uvoellger added a comment - Any information about 3.3.1? Thanks

            Eric Dalgliesh added a comment - https://studio.atlassian.com/browse/JST-3558

            Matthew Erickson added a comment - - edited

            I have attached version 1.20 of the Page Tree plugin, which fixes this issue, and has been tested with Confluence 3.3.2 and newer.

            Matthew Erickson added a comment - - edited I have attached version 1.20 of the Page Tree plugin, which fixes this issue, and has been tested with Confluence 3.3.2 and newer.

              Unassigned Unassigned
              smaddox SarahA
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: