Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-70940

Template injection in Web Resources Manager - CVE-2020-14172

XMLWordPrintable

      This issue exists to document that a security improvement in the way that Jira Server and Data Center use velocity templates has been implemented.

      The way in which velocity templates were used in Atlassian Jira Server and Data Center prior to version 8.8.1 allowed remote attackers to achieve remote code execution via insecure deserialization, if they were able to exploit a server side template injection vulnerability.

      Affected versions:

      • version < 7.13.0
      • 8.0.0 ≤ version < 8.5.0
      • 8.6.0 ≤ version < 8.8.1

      Fixed versions:

      • 8.8.1
      • 8.9.0

      Workaround for previous versions:
      You use this workaround at your own discretion.

      1. Download Jira 8.12.3 as zip and extract it’s content
      2. Localize your Jira instance installation directory
      3. Shutdown your Jira instance
      4. Go to the <jira_installation_dir>/atlassian-jira/WEB-INF/lib/ directory
      5. Remove files: velocity-htmlsafe-3.0.0.jar and velocity-1.6.4-atlassian-7.jar
      6. Copy files velocity-htmlsafe-3.1.1.jar and velocity-1.6.4-atlassian-21.jar from downloaded Jira 8.12 to current directory. They are found in the <Jira_8_12_dir>/atlassian-jira/WEB-INF/lib/ directory
      7. Go to the <jira_installation_dir>/atlassian-jira/WEB-INF/classes directory
      8. Replace the velocity.properties and velocity-static.properties files with their counterparts from the downloaded Jira 8.12.3
      9. Start your Jira instance again

            [JRASERVER-70940] Template injection in Web Resources Manager - CVE-2020-14172

            Pawel Przytarski added a comment -

            niranjan.babudhanara Workaround should be applicable for Jira 8.3.4 according to my knowledge about Jira but I didn't tested it.

            Pawel Przytarski added a comment - niranjan.babudhanara Workaround should be applicable for Jira 8.3.4 according to my knowledge about Jira but I didn't tested it.

            Pawel Przytarski added a comment -

            5717f2a94c18 we are in process of preparing 8.13 LTS. We released 8.13.0-RC1 few days ago. 8.13.0 should be release in the near future.

            Pawel Przytarski added a comment - 5717f2a94c18 we are in process of preparing 8.13 LTS. We released 8.13.0-RC1 few days ago. 8.13.0 should be release in the near future.

            Niranjan added a comment -

            Hi Pawel,

            Is this workaround applicable for Jira 8.3.4? Kindly confirm.

            Niranjan added a comment - Hi Pawel, Is this workaround applicable for Jira 8.3.4? Kindly confirm.

            Tobias added a comment -

            Hey Pawel, 

            thanks for the workaround we´ll try this if it´s necessary.

            Can you give as some information about the release time of LTS 8.13? 

            Thank you

            Tobias added a comment - Hey Pawel,  thanks for the workaround we´ll try this if it´s necessary. Can you give as some information about the release time of LTS 8.13?  Thank you

            Pawel Przytarski added a comment -
            Atlassian Update – 05 October 2020

            Hi everyone,

            thank you for all your comments and questions.

            We would like to inform you that we have been investigating the possibility of backporting the requested functionality to Jira LTS versions 7.13x and 8.5.x. Unfortunately this improvement causes problems with non-Atlassian plugins preventing them from working correctly. Due to its technical complexity we cannot provide any means of disabling it without manipulation with Jira files.
            We treat this issue as a security improvement, not a security vulnerability that can be exploited. We have made it harder for an attacker to exploit potential server-side template injection vulnerabilities in the future Jira releases.

            In the light of the above, we have decided not to backport the requested functionality to both Jira 8.5.x and 7.13.x LTS releases.

            We understand that this decision may be disappointing, however we want to assure you that we will keep treating all server-side template injection vulnerabilities as high or critical severity issues if they affect our LTS releases.

            For those customers who are currently using our LTS versions, we have prepared a workaround (please see the description field of this issue). After applying the workaround all native Jira functionality should work as before, however some 3rd party and your own internal apps may stop working or cause problems with other Jira functionality. You can use this workaround at your own discretion.

            The security improvement will be available in our upcoming 8.13 LTS release. If you have any questions or feedback about the workaround, please leave us a comment.

            Kind regards,
            Paweł Przytarski
            Jira Server Bugfix Team

            Pawel Przytarski added a comment - Atlassian Update – 05 October 2020 Hi everyone, thank you for all your comments and questions. We would like to inform you that we have been investigating the possibility of backporting the requested functionality to Jira LTS versions 7.13x and 8.5.x. Unfortunately this improvement causes problems with non-Atlassian plugins preventing them from working correctly. Due to its technical complexity we cannot provide any means of disabling it without manipulation with Jira files. We treat this issue as a security improvement, not a security vulnerability that can be exploited. We have made it harder for an attacker to exploit potential server-side template injection vulnerabilities in the future Jira releases. In the light of the above, we have decided not to backport the requested functionality to both Jira 8.5.x and 7.13.x LTS releases. We understand that this decision may be disappointing, however we want to assure you that we will keep treating all server-side template injection vulnerabilities as high or critical severity issues if they affect our LTS releases. For those customers who are currently using our LTS versions, we have prepared a workaround (please see the description field of this issue). After applying the workaround all native Jira functionality should work as before, however some 3rd party and your own internal apps may stop working or cause problems with other Jira functionality. You can use this workaround at your own discretion. The security improvement will be available in our upcoming 8.13 LTS release. If you have any questions or feedback about the workaround, please leave us a comment. Kind regards, Paweł Przytarski Jira Server Bugfix Team

            Mert Karadağlı _ Köstebek Teknoloji _ added a comment -

            Hi, 

             

            Is this bug resolved on LTS release 8.5.x?

            Mert Karadağlı _ Köstebek Teknoloji _ added a comment - Hi,    Is this bug resolved on LTS release 8.5.x?

            Tobias added a comment -

            Hello together, I also want to know if there will be a 8.5.x LTS fix. I hope we get some feedback about incoming bug fixes. Thanks

            Tobias added a comment - Hello together, I also want to know if there will be a 8.5.x LTS fix. I hope we get some feedback about incoming bug fixes. Thanks

            Sriram Subramanian added a comment -

            Hello - I am using 8.6.1 and I understand you have fixed this in 8.8 and 8.9, is there any workaround for 8.6.1 version? Would be glad to know if we get some workaround for this vulnerabilities. 

            Sriram Subramanian added a comment - Hello - I am using 8.6.1 and I understand you have fixed this in 8.8 and 8.9, is there any workaround for 8.6.1 version? Would be glad to know if we get some workaround for this vulnerabilities. 

            AB added a comment - - edited

            Hi bartelt! We've now checked 7.13.x as well. It turns out that 7.13.x isn't affected by this bug either.
            I've updated the bug description above accordingly. I'll also push the update through to Mitre's CVE registration system.

            AB added a comment - - edited Hi bartelt ! We've now checked 7.13.x as well. It turns out that 7.13.x isn't affected by this bug either. I've updated the bug description above accordingly. I'll also push the update through to Mitre's CVE registration system.

            John Bartelt added a comment -

            So what about 7.13, which is also an LTS release?

            John Bartelt added a comment - So what about 7.13, which is also an LTS release?

              Unassigned Unassigned
              security-metrics-bot Security Metrics Bot
              Affected customers:
              0 This affects my team
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: