CVE-2025-22157

This High severity PrivEsc (Privilege Escalation) vulnerability was introduced in versions:

9.12.0, 10.3.0, 10.4.0, and 10.5.0 of Jira Core Data Center and Server

5.12.0, 10.3.0, 10.4.0, and 10.5.0 of Jira Service Management Data Center and Server

This PrivEsc (Privilege Escalation) vulnerability, with a CVSS Score of 7.2, allows an attacker to perform actions as a higher-privileged user.

Atlassian recommends that Jira Core Data Center and Server and Jira Service Management Data Center and Server customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions:

Jira Core Data Center and Server 9.12: Upgrade to a release greater than or equal to 9.12.20

Jira Service Management Data Center and Server 5.12: Upgrade to a release greater than or equal to 5.12.20

Jira Core Data Center 10.3: Upgrade to a release greater than or equal to 10.3.5

Jira Service Management Data Center 10.3: Upgrade to a release greater than or equal to 10.3.5

Jira Core Data Center 10.4: Upgrade to a release greater than or equal to 10.6.0

Jira Service Management Data Center 10.4: Upgrade to a release greater than or equal to 10.6.0

Jira Core Data Center 10.5: Upgrade to a release greater than or equal to 10.5.1

Jira Service Management Data Center 10.5: Upgrade to a release greater than or equal to 10.5.1

See the release notes. You can download the latest version of Jira Core Data Center and Jira Service Management Data Center from the download center.

This vulnerability was reported via our Atlassian (Internal) program.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

Potential Mitigations

• Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
• Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/19.html
• https://cwe.mitre.org/data/definitions/441.html
• https://cwe.mitre.org/data/definitions/478.html
• https://cwe.mitre.org/data/definitions/479.html
• https://cwe.mitre.org/data/definitions/502.html
• https://cwe.mitre.org/data/definitions/503.html
• https://cwe.mitre.org/data/definitions/536.html
• https://cwe.mitre.org/data/definitions/546.html
• https://cwe.mitre.org/data/definitions/550.html
• https://cwe.mitre.org/data/definitions/551.html
• https://cwe.mitre.org/data/definitions/552.html
• https://cwe.mitre.org/data/definitions/556.html
• https://cwe.mitre.org/data/definitions/558.html
• https://cwe.mitre.org/data/definitions/562.html
• https://cwe.mitre.org/data/definitions/563.html
• https://cwe.mitre.org/data/definitions/564.html
• https://cwe.mitre.org/data/definitions/578.html

References

• https://confluence.atlassian.com/pages/viewpage.action?pageId=1561365992
• https://jira.atlassian.com/browse/JRASERVER-78766
• https://jira.atlassian.com/browse/JSDSERVER-16206