ESB-2022.3163 – [Win][UNIX/Linux] Atlassian products: CVSS (Max): None

—–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA256

===========================================================================
AUSCERT External Security Bulletin Redistribution

ESB-2022.3163
CVE-2022-26135 – Full-Read Server Side Request Forgery in
Mobile Plugin for Jira Data Center and Server
30 June 2022

===========================================================================

AusCERT Security Bulletin Summary
———————————

Product: Jira Core Server
Jira Software Server
Jira Software Data Center
Jira Service Management Server
Jira Service Management Data Center
Publisher: Atlassian
Operating System: Windows
UNIX variants (UNIX, Linux, OSX)
Resolution: Patch/Upgrade
CVE Names: CVE-2022-26135

Original Bulletin:
https://confluence.atlassian.com/jira/jira-server-security-advisory-29nd-june-2022-1142430667.html

Comment: CVSS (Max): None available when published

– ————————–BEGIN INCLUDED TEXT——————–

+————-+—————————————————————+
| Summary |CVE-2022-26135 – Full-Read Server Side Request Forgery in |
| |Mobile Plugin for Jira Data Center and Server |
+————-+—————————————————————+
| Advisory |29 Jun 2022 10:00 AM PDT (Pacific Time, -7 hours) |
|Release Date | |
+————-+—————————————————————+
| |Jira: |
| | |
| | o Jira Core Server |
| | o Jira Software Server |
| Product | o Jira Software Data Center |
| | |
| |Jira Service Management (JSM): |
| | |
| | o Jira Service Management Server |
| | o Jira Service Management Data Center |
+————-+—————————————————————+
| |Jira Core Server, Jira Software Server, and Jira Software Data |
| |Center: |
| | |
| | o Versions after 8.0 and before 8.13.22 |
| | o 8.14.x |
| | o 8.15.x |
| | o 8.16.x |
| | o 8.17.x |
| | o 8.18.x |
| | o 8.19.x |
| | o 8.20.x before 8.20.10 |
| | o 8.21.x |
| | o 8.22.x before 8.22.4 |
| Affected | |
| Versions |Jira Service Management Server and Data Center: |
| | |
| | o Versions after 4.0 and before 4.13.22 |
| | o 4.14.x |
| | o 4.15.x |
| | o 4.16.x |
| | o 4.17.x |
| | o 4.18.x |
| | o 4.19.x |
| | o 4.20.x before 4.20.10 |
| | o 4.21.x |
| | o 4.22.x before 4.22.4 |
| | |
| |Jira Cloud and Jira Service Management Cloud are not affected. |
+————-+—————————————————————+
| |Jira Core Server, Jira Software Server, and Jira Software Data |
| |Center: |
| | |
| | o 8.13.x >= 8.13.22 |
| | o 8.20.x >= 8.20.10 |
| | o 8.22.x >= 8.22.4 |
| Fixed | o 9.0.0 |
| Versions | |
| |Jira Service Management Server and Data Center: |
| | |
| | o 4.13.x >= 4.13.22 |
| | o 4.20.x >= 4.20.10 |
| | o 4.22.x >= 4.22.4 |
| | o 5.0.0 |
+————-+—————————————————————+
| CVE ID(s) |CVE-2022-26135 |
+————-+—————————————————————+

Summary of Vulnerability

This advisory discloses a high severity security vulnerability.

Jira Server and Data Center versions before 8.13.22, from version 8.14.0 before
8.20.10, and from version 8.21.0 before 8.22.4 are affected by this
vulnerability.

Jira Service Management Server and Data Center versions before 4.13.22, from
version 4.14.0 before 4.20.10, and from version 4.21.0 before 4.22.4 are
affected by this vulnerability.

+—————————————————————————–+
|Atlassian Cloud sites are not affected. |
| |
|If your Jira site is accessed via an atlassian.net domain, you are not |
|affected by the vulnerability. |
+—————————————————————————–+
+—————————————————————————–+
|Customers who have upgraded to version 8.13.22, 8.20.10, 8.22.4, or 9.0.0 of |
|Jira Server or Data Center are not affected. |
| |
|Customers who have upgraded to version 4.13.22, 4.20.10, 4.22.4, or 5.0.0 of |
|Jira Service Management Server or Data Center are not affected. |
+—————————————————————————–+
+—————————————————————————–+
|Customers who have downloaded and installed any versions listed in affected |
|versions must upgrade their installations to fix this vulnerability. |
| |
|Please upgrade your installations immediately. |
+—————————————————————————–+

CVE-2022-26135 Full Read SSRF in Jira Server

Description

A full-read server-side request forgery exists in Mobile Plugin for Jira, which
is bundled with Jira and Jira Service Management. It is exploitable by any
authenticated user (including a user who joined via the sign-up feature). It
specifically affects the batch HTTP endpoint used in Mobile Plugin for Jira. It
is possible to control the HTTP method and location of the intended URL through
the method parameter in the body of the vulnerable endpoint.

All versions of Jira and Jira Service Management prior to the fixed version
listed above are affected by this vulnerability. These issues can be tracked
here:

o JRASERVER-73863 – Getting issue details… STATUS
o JSDSERVER-11840 – Getting issue details… STATUS

This does not affect the other System app named Jira Mobile.

Severity

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

Depending on the environment the Jira instance is deployed in, the impact of
this bug varies. For example, when deployed in AWS, it could leak sensitive
credentials.

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

Acknowledgements

We would like to acknowledge Shubham Shah and Dylan Pindur of Assetnote for
finding this vulnerability.

Fix

To address this issue, we have released:

o Jira Core Server, Jira Software Server, and Jira Software Data Center
versions:
o 8.13.22
o 8.20.10
o 8.22.4
o 9.0.0
o Jira Service Management Server and Data Center versions:
o 4.13.22
o 4.20.10
o 4.22.4
o 5.0.0

You can download the latest versions from the download pages for Jira Core,
Jira Software, or Jira Service Management.

Please note, these are the first versions that include the fix for
CVE-2022-26135. More current bug fix releases are available for the releases
listed above. Atlassian recommends upgrading to the most current bug fix
version.

Mitigation

Installing a fixed version of Jira or Jira Service Management is the surest way
to remediate CVE-2022-26135. If you are unable to immediately upgrade Jira or
Jira Service Management, then as a temporary workaround, you can manually
upgrade Mobile Plugin for Jira Data Center and Server
(com.atlassian.jira.mobile.jira-mobile-rest) to the versions specified in this
section (or disable the plugin).

The following versions of the Mobile Plugin for Jira app contain a fix for this
issue:

o 3.1.5 (only compatible with Jira 8.13.x and JSM 4.13.x)
o 3.2.15 (only compatible with Jira 8.20.x – 8.22.x, only compatible with JSM
4.20.x – 4.22.x)

If you’re either on Jira 8.13.x or JSM 4.13.x and have previously upgraded
beyond the default app version of 3.1.x, upgrading to 3.1.5 will effectively
roll back any bug-fixes and features introduced in later versions, including
JSM support.

How to upgrade the app

Scenario A: User-installed apps

If you find the “Mobile Plugin for Jira” app located in the User-installed apps
section, you can just click Update to get the latest version.

Scenario B: System apps

If you find the “Mobile Plugin for Jira” app located in the System apps
section, follow these instructions to manually update the app (no restart
required!):

1. Download a fixed version of the app (you’ll save this as a JAR file) from
the Atlassian Marketplace that is compatible with your Jira version
2. During a maintenance window:
1. Navigate to Admin > Manage Apps
2. Select Upload app
3. Select the JAR file you downloaded in Step 1
3. After the install, the new version will be displayed as a user-installed
app instead of a system app.

o The previous JAR file can remain in the directory /
atlassian-jira/WEB-INF/atlassian-bundled-plugins without further action.

Support

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 read our FAQ
for CVE-2022-26135. If you have further questions, please raise a support
request.

Last modified on Jun 29, 2022

– ————————–END INCLUDED TEXT——————–

You have received this e-mail bulletin as a result of your organisation’s
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT’s members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation’s
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.

NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author’s website to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:

https://www.auscert.org.au/bulletins/

===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072

Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
—–BEGIN PGP SIGNATURE—–
Comment: https://auscert.org.au/gpg-key/

iQIVAwUBYr0aPskNZI30y1K9AQg3yQ/9FRUOPVjFQdoJmTEnBaFCjRJ89MU9HmqR
2KBV7gfjbPBeRI4g1wUzLXq20HqnOYP6cxe8VqdKm0WD2uO28SsF6RLxRCW1fiXY
RHxLpq5RqFMWue+M9zlVeoqKh5M2qfsNI+W2p7PEQnfdiiDawDUTjZi2P3uO9KCG
ivPhzJyt12To16HW+jCyuHAwI0Ngl5cyo7A4PzGQatobvLqz/I8RDEnvlLU7cCON
0m9LZ9gzuBObRgOh6/DjgjtiQUsvb8O6iPkrJf2ZFfY9Hawa22YZQKoi52RBT1Nc
3aMX3tMvpqtmvsIzac1wf/jqG4ca7mDvkn5+JOlTqJWY0AwEs3Y2FKNUxhe90RaV
WotPOsOurLJ2rS47IYv4qafVcDIv8+dO4gIy5BZI0xO0EyWh6X4+kGZWY9YgAu6q
6TSX5DBDXC4CAPjI/OPMY/vuusmJPHRGTvvxZeHqjuu5le5Q25OPsiGPg1TbxJwb
kmlJRxfxBEGMfbOCK67av7ZJi0HnUl9CJlkBQF+EqPtOenHhMfEqas0ZMxPsakEk
9xmarh4jMDazlGSNQlt8uWa8Tgc0XN+X87PoBS74JXJCsLDBrJNXDPvP5WxPkbr8
GukGKlCj/2jXr8WL4rICzGP+VBFFAWjm6elBi/fTpfFbSnE/WGKal0YMZfpk+zyv
EJNSPLVQPds=
=n3Lm
—–END PGP SIGNATURE—–Security BulletinsRead More