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

This Critical severity Security Headers Omission vulnerability was introduced in versions 10.3.0 and 11.3.0 of Jira Software Data Center.

This Security Headers Omission 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 receive responses where security HTTP headers (such as Cache-Control, X-Frame-Options, and X-Content-Type-Options) are silently omitted, enabling secondary attacks such as clickjacking, cache poisoning, or MIME-type sniffing, which has high impact to confidentiality, high impact to integrity, no 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 10.3: Upgrade to a release greater than or equal to 10.3.7
• Jira Software Data Center 11.3: Upgrade to a release greater than or equal to 11.3.5

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: When applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written. This issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers: from 5.7.0 through 5.7.21, from 5.8.0 through 5.8.23, from 6.3.0 through 6.3.14, from 6.4.0 through 6.4.14, from 6.5.0 through 6.5.8, and from 7.0.0 through 7.0.3.