confluence.atlassian.com Open in urlscan Pro
2600:9000:214f:fa00:15:77aa:5e80:93a1  Public Scan

Form analysis
2 forms found in the DOM

<form><span class="fieldset">
    <p><input type="checkbox" value="check" id="chkMain" checked="checked" class="legacy-group-status optanon-status-checkbox"><label for="chkMain">Active</label></p>
  </span></form>

<form>
  <radiogroup>
    <div class="reason-radio-box">
      <label><input type="radio" name="was-this-helpful-no-reason" value="It wasn't accurate"> It wasn't accurate</label>
    </div>
    <div class="reason-radio-box">
      <label><input type="radio" name="was-this-helpful-no-reason" value="It wasn't clear"> It wasn't clear</label>
    </div>
    <div class="reason-radio-box">
      <label><input type="radio" name="was-this-helpful-no-reason" value="It wasn't relevant"> It wasn't relevant</label>
    </div>
  </radiogroup>
</form>

Text Content

Cookie Notice

This site uses cookies to improve your browsing experience, perform analytics
and research, and conduct advertising. To change your preferences, click Cookie
Settings. Otherwise, clicking on the the website, closing the banner, or
clicking Accept all Cookies indicates you agree to our use of cookies on your
device. Atlassian Cookies and Tracking Notice


Close
Accept all Cookies
Cookie Settings


 * Your Privacy

 * Strictly Necessary Cookies

 * Performance and Analytics Cookies

 * Functional Cookies

 * Targeting Cookies

 * Atlassian Cookies and Tracking Notice

Privacy Preference Centre

Active

Always Active



Save Settings

Allow All



 * Products
 * Resources

 * Search
 * Log in
 *  * View account
    * View requests
    * Log out

 * ...


PRODUCTS


 * JIRA SOFTWARE
   
   Project and issue tracking


 * JIRA SERVICE MANAGEMENT
   
   Service management and customer support


 * JIRA WORK MANAGEMENT
   
   Manage any business project


 * CONFLUENCE
   
   Document collaboration


 * BITBUCKET
   
   Git code management

See all


RESOURCES


 * DOCUMENTATION
   
   Usage and admin help


 * COMMUNITY
   
   Answers, support, and inspiration


 * SYSTEM STATUS
   
   Cloud services health


 * SUGGESTIONS AND BUGS
   
   Feature suggestions and bug reports


 * MARKETPLACE
   
   Product apps


 * BILLING AND LICENSING
   
   Frequently asked questions

 * Log out
 * Log in to account
 * List watched pages
 * Contact support
 * Training & Certification
 * Cloud Migration Center
 * GDPR guides
 * Enterprise services
 * Atlassian partners
 * Developers
 * User groups
 * Automation for Jira
 * Atlassian.com

 * PAGE

 * View in Confluence
 * Edit Page

 * VIEWPORT

 * Manage Viewport

 * CONFLUENCE

 * Dashboard
 * Space Directory
 * People Directory

JIRA 6.4.x

Documentation

Unable to load

 * Atlassian Support
 * Documentation
 * JIRA 6.4.x
 * JIRA Releases
 * Security Advisories
 * Jira Service Management Server and Data Center Advisory (CVE-2023-22501)




JIRA SERVICE MANAGEMENT SERVER AND DATA CENTER ADVISORY (CVE-2023-22501)

SECURITY ADVISORIES

 * JIRA Security Advisory 2007-12-24
 * JIRA Security Advisory 2008-02-21
 * JIRA Security Advisory 2008-08-26
 * JIRA Security Advisory 2008-10-29
 * JIRA Security Advisory 2008-12-09
 * JIRA Security Advisory 2009-04-02
 * JIRA Security Advisory 2010-04-16
 * JIRA Security Advisory 2010-06-18
 * JIRA Security Advisory 2010-12-06
 * JIRA Security Advisory 2011-02-21
 * JIRA Security Advisory 2011-09-27
 * JIRA Security Advisory 2012-05-17
 * JIRA Security Advisory 2012-08-28
 * JIRA Security Advisory 2013-02-21
 * JIRA Security Advisory 2014-02-26
 * JIRA and HipChat for JIRA plugin Security Advisory 2015-08-26
 * JIRA Security Advisory 2015-12-09
 * JIRA and HipChat for JIRA plugin Security Advisory 2016-09-21
 * JIRA Security Advisory 2017-03-09
 * JIRA Security Advisory 2019-07-10
 * Jira Service Desk Security Advisory 2019-09-18
 * Jira Security Advisory 2019-09-18
 * Jira Service Desk Security Advisory 2019-11-06
 * Jira Server for Slack Security Advisory 17th February 2021
 * Jira Security Advisory 2022-04-20
 * Jira Server Security Advisory 29nd June 2022
 * Jira Service Management Server and Data Center Advisory (CVE-2023-22501)

ON THIS PAGE

STILL NEED HELP?

The Atlassian Community is here for you.

Ask the community

Summary

CVE-2023-22501 - Broken Authentication vulnerability in Jira Service Management

Advisory Release Date

01 February 2023 10:00 AM PDT (Pacific Time, -7 hours)

Product

 * Jira Service Management Server

 * Jira Service Management Data Center

CVE ID(s)

CVE-2023-22501


SUMMARY OF VULNERABILITY

This advisory discloses a critical severity security vulnerability which was
introduced in version 5.3.0 of Jira Service Management Server and Data
Center. The following versions are affected by this vulnerability:

 * 5.3.0

 * 5.3.1

 * 5.3.2

 * 5.4.0

 * 5.4.1

 * 5.5.0

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.



The issue can be tracked here: JSDSERVER-12312 - Critical severity
authentication vulnerability - CVE-2023-22501 Published

Atlassian Cloud sites are not affected.

If your Jira site is accessed via an atlassian.net domain, it is hosted by
Atlassian and you are not affected by the vulnerability.


SEVERITY

Atlassian rates the severity level of this vulnerability as critical, according
to the scale published in our Atlassian severity levels. The scale allows us to
rank the severity as critical, high, moderate or low.

This is our assessment and you should evaluate its applicability to your own IT
environment.


AFFECTED VERSIONS

Jira Service Management Server and Data Center versions 5.3.0 to 5.3.1 and 5.4.0
to 5.5.0 are affected by this vulnerability.

Product

Affected Versions

Jira Service Management Server and Data Center

 * 5.3.0

 * 5.3.1

 * 5.3.2

 * 5.4.0

 * 5.4.1

 * 5.5.0


FIXED VERSIONS

Product

Fixed Versions

Jira Service Management Server and Data Center

 * 5.3.3

 * 5.4.2

 * 5.5.1

 * 5.6.0 or later


WHAT YOU NEED TO DO

Atlassian recommends that you upgrade each of your affected installations to one
of the listed fixed versions (or any later version) above (see the “Fixed
Versions” section of this page for details). For a full description of the
latest version of Jira Service Management Server and Data Center, see the
release notes. You can download the latest version of Jira Service Management
and Data Center from the download center. For Frequently Asked Questions (FAQ),
click here.

MITIGATION

Installing a fixed version of Jira Service Management is the recommended way to
remediate this vulnerability. If you are unable to immediately upgrade Jira
Service Management, you can manually upgrade the version-specific
servicedesk-variable-substitution-plugin JAR file as a temporary workaround.

Jira Service Management Versions

JAR File

5.5.0

servicedesk-variable-substitution-plugin-5.5.1-REL-0005.jar

5.4.0, 5.4.1

servicedesk-variable-substitution-plugin-5.4.2-REL-0005.jar

5.3.0, 5.3.1, 5.3.2

servicedesk-variable-substitution-plugin-5.3.3-REL-0001.jar

To update the servicedesk-variable-substitution-plugin JAR file:

 1. Download the version-specific JAR file from the table above.
 2. Stop Jira.

 3. Copy the JAR file into your Jira home directory.
    
    1. For Server: <Jira_Home>/plugins/installed-plugins
    
    2. For Data Center: <Jira_Shared>/plugins/installed-plugins
 4. Start Jira.


DETECTION

Atlassian cannot confirm if your instance has been affected by this
vulnerability, but there are some steps you can follow to investigate your
instances for potential unauthorized access. You can see the detailed steps
outlined on the Frequently Asked Questions (FAQ) page here.


SUPPORT

For Frequently Asked Questions (FAQ), click here. 

If you did not receive an email for this advisory and you wish to receive such
emails in the future go to https://my.atlassian.com/email and subscribe
to Alerts emails.

If you have questions or concerns regarding this advisory, please raise a
support request at https://support.atlassian.com/.


REFERENCES

Security Bug fix Policy



As per our new policy critical security bug fixes will be back ported in
accordance with https://www.atlassian.com/trust/security/bug-fix-policy.  We
will release new maintenance releases for the versions covered by the policy
instead of binary patches.

Binary patches are no longer released. 

Severity Levels for security issues



Atlassian security advisories include a severity level and a CVE identifier.
This severity level is based on our self-calculated CVSS score for each specific
vulnerability. CVSS is an industry standard vulnerability metric. You can also
learn more about CVSS at FIRST.org.

End of Life Policy



 Our end of life policy varies for different products. Please refer to our EOL
Policy for details. 

Last modified on Feb 1, 2023


Was this helpful?

Yes
No
It wasn't accurate
It wasn't clear
It wasn't relevant
Provide feedback about this article

Powered by Confluence and Scroll Viewport.
Atlassian
 * Privacy policy
 * Terms of use
 * Security
 * © 2023 Atlassian