-
Type:
Public Security Vulnerability
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 11.3.7, 11.3.8, 11.3.9, 11.3.10, 10.3.22, 10.3.23
-
Component/s: None
-
8.1
-
High
-
CVE-2026-101905
-
Atlassian (Internal)
-
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
-
MITM (Man-in-the-Middle)
-
Jira Service Management Data Center
This High severity MITM (Man-in-the-Middle) vulnerability was introduced in versions 10.3.22 and 11.3.7 of Jira Service Management Data Center.
This MITM (Man-in-the-Middle) vulnerability, with a CVSS Score of 8.1 and a CVSS Vector of CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N allows an authenticated attacker to potentially interdict connections to remote hosts, which has high impact to confidentiality, high 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.11
- 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:
Axios is a promise-based HTTP client for the browser and Node.js. From 1.15.2 until 1.20.0, the Node HTTP adapter in lib/adapters/http.js supplies request options without an own createConnection value. A separate same-process prototype-pollution flaw places a function on Object.prototype.createConnection. Node resolves and invokes the inherited createConnection socket factory, allowing the attacker-controlled function to select the transport endpoint. The attacker endpoint can receive request headers and bodies, including credentials, and return attacker-controlled responses while the URL appears legitimate. This issue is fixed in version 1.20.0.
- mentioned in
-
Page Loading...