• 9.4
    • Critical
    • CVE-2023-22501

      An authentication vulnerability was discovered in Jira Service Management Server and Data Center which allows an attacker to impersonate another user and gain access to a Jira Service Management instance under certain circumstances. With write access to a User Directory and outgoing email enabled on a Jira Service Management instance, an attacker could gain access to signup tokens sent to users with accounts that have never been logged into. Access to these tokens can be obtained in two cases:

      • If the attacker is included on Jira issues or requests with these users, or
      • If the attacker is forwarded or otherwise gains access to emails containing a “View Request” link from these users.

      Bot accounts are particularly susceptible to this scenario. On instances with single sign-on, external customer accounts can be affected in projects where anyone can create their own account.

      Affected versions:

      • 5.3.0
      • 5.3.1
      • 5.3.2
      • 5.4.0
      • 5.4.1
      • 5.5.0

      Fixed versions:

      • 5.3.3
      • 5.4.2
      • 5.5.1
      • 5.6.0

            [JSDSERVER-12312] Critical severity authentication vulnerability - CVE-2023-22501

            Chung Park Chan made changes -
            Labels Original: advisory advisory-to-release dont-import hot-jira-fixed security 🔢✅ New: advisory advisory-to-release dont-import security 🔢✅
            Aline Staudt made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 732814 ]
            polshettiwar kalyani made changes -
            Comment [ How can I check the current version of Jira cloud ? ]
            Security Metrics Bot made changes -
            CVE ID New: CVE-2023-22501
            Mohit Sharma made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 727402 ]
            Lee Meinecke made changes -
            Comment [ Who in the world is still running Jira 5.x in Feb 2023!?  ]
            Daniel R made changes -
            Labels Original: advisory advisory-to-release dont-import security 🔢✅ New: advisory advisory-to-release dont-import hot-jira-fixed security 🔢✅
            Arshita Sandhiparthi made changes -
            Resolution New: Fixed [ 1 ]
            Security Original: Atlassian Staff [ 10750 ]
            Status Original: Draft [ 12872 ] New: Published [ 12873 ]
            Arshita Sandhiparthi made changes -
            Description Original: An authentication vulnerability was discovered in Jira Service Management Server and Data Center which allows an attacker to impersonate another user and gain access to a Jira Service Management instance under certain circumstances{_}.{_} With public signup enabled on a Jira Service Management instance, an attacker could gain access to signup tokens sent to users with accounts that have never been logged into. Access to these tokens can be obtained in two cases:
             * If the attacker is included on Jira issues or requests with these users, or

             * If the attacker is forwarded or otherwise gains access to emails containing a “View Request” link from these users.

            Bot accounts are particularly susceptible to this scenario. On instances with single sign-on, external customer accounts can be affected in projects where anyone can create their own account.

            *Affected versions:*
             * 5.3.0

             * 5.3.1

             * 5.3.2

             * 5.4.0

             * 5.4.1

             * 5.5.0

            *Fixed versions:*
             * 5.3.3
             * 5.4.2
             * 5.5.1
             * 5.6.0
            New: An authentication vulnerability was discovered in Jira Service Management Server and Data Center which allows an attacker to impersonate another user and gain access to a Jira Service Management instance under certain circumstances{_}.{_} With write access to a User Directory and outgoing email enabled on a Jira Service Management instance, an attacker could gain access to signup tokens sent to users with accounts that have never been logged into. Access to these tokens can be obtained in two cases:
             * If the attacker is included on Jira issues or requests with these users, or

             * If the attacker is forwarded or otherwise gains access to emails containing a “View Request” link from these users.

            Bot accounts are particularly susceptible to this scenario. On instances with single sign-on, external customer accounts can be affected in projects where anyone can create their own account.

            *Affected versions:*
             * 5.3.0

             * 5.3.1

             * 5.3.2

             * 5.4.0

             * 5.4.1

             * 5.5.0

            *Fixed versions:*
             * 5.3.3
             * 5.4.2
             * 5.5.1
             * 5.6.0
            Daniel R made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 727105 ]

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

                Created:
                Updated:
                Resolved: