We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-73138

Default field configuration can be restored via CSRF - CVE-2021-43952

XMLWordPrintable

    • 3
    • Low
    • CVE-2021-43952

      Affected versions of Atlassian Jira Server and Data Center allow authenticated remote attackers to restore the default configuration of fields via a Cross-Site Request Forgery (CSRF) vulnerability in the /secure/admin/RestoreDefaults.jspa endpoint.

      This bug is currently fixed on Jira 8.21.0.
      Non LTS versions < 8.21.0 are still affected.

      Previous LTS versions affected by this bug: 

      • Jira < 8.20.6 and Jira < 8.13.18

      The bug fix was backported to the following previous LTS version patches:

      • Fixed on Jira 8.20.6 and 8.13.18

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-73138

            Default field configuration can be restored via CSRF - CVE-2021-43952

            XMLWordPrintable

              • 3
              • Low
              • CVE-2021-43952

                Affected versions of Atlassian Jira Server and Data Center allow authenticated remote attackers to restore the default configuration of fields via a Cross-Site Request Forgery (CSRF) vulnerability in the /secure/admin/RestoreDefaults.jspa endpoint.

                This bug is currently fixed on Jira 8.21.0.
                Non LTS versions < 8.21.0 are still affected.

                Previous LTS versions affected by this bug: 

                • Jira < 8.20.6 and Jira < 8.13.18

                The bug fix was backported to the following previous LTS version patches:

                • Fixed on Jira 8.20.6 and 8.13.18

                        Unassigned Unassigned
                        security-metrics-bot Security Metrics Bot
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        16 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            security-metrics-bot Security Metrics Bot
                            Votes:
                            0 Vote for this issue
                            Watchers:
                            16 Start watching this issue

                              Created:
                              Updated:
                              Resolved: