This is a vulnerability in a non-Atlassian dependency. Atlassian's application of this dependency presents a lower, non-critical assessed risk.

This Critical severity Injection vulnerability was introduced in versions 5.17.2, 10.3.12, 11.1.0, 11.2.0, and 11.3.0 of Jira Service Management Data Center.

This Injection vulnerability, with a CVSS Score of 9.1 and a CVSS Vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N allows an unauthenticated attacker to modify the actions taken by a system call 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.7
• Jira Service Management Data Center 10.3: Upgrade to a release greater than or equal to 10.3.22

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 version 1.0.0 to before version 1.15.2, fFive config properties (auth, baseURL, socketPath, beforeRedirect, and insecureHTTPParser) in the HTTP adapter are read via direct property access without hasOwnProperty guards, making them exploitable as prototype pollution gadgets. When Object.prototype is polluted by another dependency in the same process, axios silently picks up these polluted values on every outbound HTTP request. This issue has been patched in version 1.15.2.