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

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

      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

            AB made changes -
            Description Original: 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.
            {quote}
            1. Download [Jira 8.12.3|https://product-downloads.atlassian.com/software/jira/downloads/atlassian-jira-software-8.12.3.zip] as zip and extract it’s content
            2. [Localize your Jira instance installation directory|https://confluence.atlassian.com/adminjiraserver/jira-application-installation-directory-938847745.html]
            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
            {quote}
            New: 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.
            {quote}1. Download [Jira 8.12.3|https://product-downloads.atlassian.com/software/jira/downloads/atlassian-jira-software-8.12.3.zip] as zip and extract it’s content
            2. [Localize your Jira instance installation directory|https://confluence.atlassian.com/adminjiraserver/jira-application-installation-directory-938847745.html]
            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
            {quote}
            Tiziana Marchionni made changes -
            Description Original: 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.
            {quote}
            1. Download [Jira 8.12.3|https://product-downloads.atlassian.com/software/jira/downloads/atlassian-jira-software-8.12.3.zip] as zip and extract it’s content
            2. [Localize your Jira instance installation directory|https://confluence.atlassian.com/adminjiraserver/jira-application-installation-directory-938847745.html]
            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.0.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
            {quote}
            New: 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.
            {quote}
            1. Download [Jira 8.12.3|https://product-downloads.atlassian.com/software/jira/downloads/atlassian-jira-software-8.12.3.zip] as zip and extract it’s content
            2. [Localize your Jira instance installation directory|https://confluence.atlassian.com/adminjiraserver/jira-application-installation-directory-938847745.html]
            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
            {quote}
            Tiziana Marchionni made changes -
            Description Original: 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.
            {quote}
            1. Download [Jira 8.12|https://product-downloads.atlassian.com/software/jira/downloads/atlassian-jira-software-8.12.2.zip] as zip and extract it’s content
            2. [Localize your Jira instance installation directory|https://confluence.atlassian.com/adminjiraserver/jira-application-installation-directory-938847745.html]
            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.0.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
            9. Start your Jira instance again
            {quote}
            New: 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.
            {quote}
            1. Download [Jira 8.12.3|https://product-downloads.atlassian.com/software/jira/downloads/atlassian-jira-software-8.12.3.zip] as zip and extract it’s content
            2. [Localize your Jira instance installation directory|https://confluence.atlassian.com/adminjiraserver/jira-application-installation-directory-938847745.html]
            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.0.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
            {quote}
            David Black made changes -
            Labels Original: CVE-2020-14172 advisory advisory-to-release bugbounty cvss-high injection security template-injection New: CVE-2020-14172 advisory advisory-released bugbounty cvss-high injection security template-injection
            Mark Lang made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 511691 ]
            ali made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 509882 ]
            ali made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 509631 ]
            Mark Lang made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 508419 ]

            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.

            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.

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

                Created:
                Updated:
                Resolved: