-
Type:
Public Security Vulnerability
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 5.17.0, 10.0.0, 10.0.1, 10.1.1, 10.1.2, 10.2.0, 10.2.1, 10.3.0, 10.3.1, 10.3.2, 10.3.3, 10.3.4, 10.3.5, 10.3.6, 10.3.7, 10.3.8, 10.3.9, 10.3.10, 10.3.11, 10.3.12, 10.3.13, 10.3.14, 10.3.15, 10.4.0, 10.4.1, 10.5.0, 10.5.1, 10.6.0, 10.6.1, 10.7.1, 10.7.2, 10.7.3, 10.7.4, 11.0.0, 11.1.0, 11.0.1, 11.1.1, 11.2.0, 11.2.1, 11.3.0, 11.3.1, 11.3.2, 11.3.3, 11.3.4, 11.3.5, 11.3.6, 11.3.7, 10.3.16, 10.3.17, 10.3.18, 10.3.19, 10.3.20, 10.3.21, 10.3.22, 10.3.23
-
Component/s: None
-
7.5
-
High
-
CVE-2026-50010
-
Atlassian (Internal)
-
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
-
Jira Service Management Data Center
This MITM (Man-in-the-Middle) vulnerability was introduced in versions 5.17.0, 10.0.0, 10.1.1, 10.2.0, 10.3.0, 10.4.0,
10.5.0, 10.6.0, 10.7.1, 11.0.0, 11.1.0, 11.2.0, and 11.3.0 of Jira Service Management Data Center and Server.
This MITM (Man-in-the-Middle) vulnerability, with a CVSS Score of 7.5 and a CVSS Vector of
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N allows an unauthenticated attacker to interdict communication with remote
systems, which has high impact to confidentiality, no impact to integrity, no impact to availability, and requires no
user interaction.
Atlassian recommends that Jira Service Management Data Center customers upgrade to latest version, if you are unable to
do so, upgrade your instance to one of the specified supported fixed versions:
- Jira Service Management Data Center 11.3: Upgrade to a release greater than or equal to 11.3.8
- Jira Service Management Data Center 10.3: Upgrade to a release greater than or equal to 10.3.24
See the release notes
(https://confluence.atlassian.com/servicemanagement/jira-service-management-release-notes-780083086.html). You can
download the latest version of Jira Service Management Data Center from the download center
(https://www.atlassian.com/software/jira/service-management/download-archives).
The National Vulnerability Database provides the following description for this vulnerability:
Netty is a network application framework for development of protocol servers and clients. Prior to versions
4.1.135.Final and 4.2.15.Final, SimpleTrustManagerFactory.engineGetTrustManagers() and related paths wrap any
user-supplied plain X509TrustManager in X509TrustManagerWrapper, which extends X509ExtendedTrustManager but implements
the 3-arg checkServerTrusted(chain, authType, SSLEngine) by discarding the SSLEngine and calling the 2-arg delegate.
Because the object now IS an X509ExtendedTrustManager, neither SunJSSE's internal AbstractTrustManagerWrapper nor
Netty's own OpenSslX509TrustManagerWrapper will re-wrap it to add endpoint-identification. Consequently, even though
Netty 4.2 sets endpointIdentificationAlgorithm="HTTPS" by default, a client built with
`SslContextBuilder.forClient().trustManager(somePlainX509TrustManager)` performs no hostname verification at all.
Versions 4.1.135.Final and 4.2.15.Final patch the issue.