This High severity MITM (Man-in-the-Middle) vulnerability was introduced in versions 10.3.13 and 11.3.0 of Jira Service Management Data Center.

This MITM (Man-in-the-Middle) vulnerability, with a CVSS Score of 7.2 and a CVSS Vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N allows an unauthenticated attacker to potentially interdict connections to remote hosts, which has low impact to confidentiality, low 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.13.0 until 1.20.0, Axios HTTP/2 request setup does not consistently apply proxy settings and caller-supplied DNS lookup policy. An HTTPS request uses httpVersion: 2 with explicit config.proxy or environment-derived proxy settings, or relies on caller-supplied config.lookup DNS policy. The HTTP/2 path can connect without the configured proxy behavior or without applying the caller-supplied config.lookup policy before http2.connect(). Requests can bypass the intended proxy route or the caller-supplied DNS resolution policy. This issue is fixed in version 1.20.0.