This High severity Prototype Pollution vulnerability was introduced in versions 10.3.0 and 11.3.7 of Jira Software Data Center.

This Prototype Pollution vulnerability, with a CVSS Score of 8.2 and a CVSS Vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H allows an unauthenticated attacker to expose assets in your environment susceptible to exploitation, which has no impact to confidentiality, low impact to integrity, high impact to availability, and requires no user interaction.

Atlassian recommends that Jira Software 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 Software Data Center 11.3: Upgrade to a release greater than or equal to 11.3.8
• Jira Software Data Center 10.3: Upgrade to a release greater than or equal to 10.3.24

See the release notes (https://www.atlassian.com/software/jira/download-archives). You can download the latest version
of Jira Software Data Center from the download center (https://www.atlassian.com/software/jira/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 0.28.0 until 0.34.0 and 1.15.1 until 1.20.0, ToFormData processes inherited serialization options and visitor properties supplied through prototype pollution. A separate same-process prototype-pollution flaw supplies inherited dots, indexes, metaTokens, maxDepth, visitor, or Blob values before object serialization. The inherited options alter toFormData field naming and data interpretation, maxDepth can force request failure, Blob changes value handling, and a polluted visitor can execute when an attacker already has the stronger ability to inject a function. Serialized field naming and data interpretation can change, maxDepth can cause request failure, Blob can alter value handling, and a polluted visitor can execute under the stronger function-injection primitive. This issue is fixed in versions 0.34.0 and 1.20.0.